Skip to content

Add gmail:search top-level tool #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
allenhutchison merged 2 commits into from
Dec 2, 2025
Merged

Add gmail:search top-level tool #47

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
98c5b20
feat: add gmail:search top-level tool
google-labs-jules[bot] Nov 27, 2025
b9f95a2
Merge pull request #1 from raybellwaves/gmail-search-command
raybellwaves Nov 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions commands/gmail/search.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
description = "Searches for emails in Gmail matching a query."
prompt = """
You are tasked with searching Gmail for emails.

1) The user's search query is: {{args}}
2) Call the `gmail.search` tool, passing the user's query as the `query` argument.
3) The `gmail.search` tool returns a JSON object containing a list of emails (id and threadId).
4) For each email found, you MUST call `gmail.get` with the `messageId` and `format='metadata'` to get the From, Subject, and Snippet.
5) Format the result into a clear, readable list.
6) If no emails are found, state that clearly.
Comment on lines +6 to +10
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Nov 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The current instructions can lead to performance issues. If a search query returns many results, the instruction in step 4 (For each email found, you MUST call 'gmail.get'...) will trigger a large number of subsequent API calls (an N+1 problem). This can result in slow responses and could potentially hit API rate limits.

To make this more efficient and provide a better user experience, I recommend explicitly limiting the number of results in the initial search and then informing the user if more results are available. The gmail.search tool returns a resultSizeEstimate which can be used for this.

2) Call the `gmail.search` tool, passing the user's query as the `query` argument and setting `maxResults` to 5.
3) The `gmail.search` tool returns a JSON object containing a list of emails (id and threadId) and a `resultSizeEstimate`.
4) For each email found, you MUST call `gmail.get` with the `messageId` and `format='metadata'` to get the From, Subject, and Snippet.
5) Format the result into a clear, readable list. If the `resultSizeEstimate` is greater than the number of emails shown, inform the user (e.g., "Showing 5 of 27 results.").
6) If no emails are found, state that clearly.


Example Output Format:
> From: sender@example.com
Subject: Meeting Reminder
Snippet: Don't forget about the meeting tomorrow...
---
> From: newsletter@example.com
Subject: Weekly News
Snippet: Here are the top stories for this week...
"""