Grain

Fetches information about a single HubSpot deal by ID. In addition to returning the same data as returned by list_all_deals, this returns data about all the activity that has occurred on the deal.

fetch_deal

Fetches information about a single Grain meeting by ID. The response format is the same as is returned by list_meetings.

fetch_meeting

Fetches the action items extracted from a single Grain meeting by ID. Each action item includes the task description, timestamp, status (pending or completed), the assignee (name, identifier and user_id, or null when unassigned), and the due date (or null when not set). `end_timestamp_ms` is null when the action item has no end time. In some cases, older meetings may not have had action items generated for them.

fetch_meeting_action_items

Fetches AI-generated sales coaching feedback and scorecard for a single Grain meeting by ID. The response format is the same as is returned by list_coaching_feedback.

fetch_meeting_coaching_feedback

Fetches the AI notes payload from a single Grain meeting by ID. In some cases, older meetings may not have had notes generated for them. In these cases you can use `fetch_meeting_transcript` instead to determine the content of the meeting.

fetch_meeting_notes

Fetches the full transcript of a single Grain meeting by ID. Returns the entire conversation as markdown, which can be large for long meetings.

fetch_meeting_transcript

Fetches the current user's private notes for a single Grain meeting by ID. Returns the notes as markdown text, or a message if no notes exist. Lines written while the meeting was recording start with a `[MM:SS]` or `[H:MM:SS]` timestamp marking that moment in the recording, in the same format as `fetch_meeting_transcript`. Convert it to milliseconds to use it with `create_clip`.

fetch_user_recording_notes

Returns a filtered list of Grain meetings you have attended, ordered by most recent. If the list contains more than `limit` meetings, the response will also contain a non-null `cursor` value that can be used to fetch the next page of meetings in the list by calling the tool again and passing the `cursor` along with the same `filters`. The list will be empty if there are no meetings matching the supplied filters. If also looking to include meetings the user didn't attend, use `list_meetings` instead. Use this when the user asks which meetings they had. For "what did we decide / discuss / know about X" questions, call `recall_meeting_memory` first instead of listing meetings.

list_attended_meetings

Returns a paginated list of Grain collections (also known as playlists) you have access to, ordered by most recent. A collection is a curated group of meetings (recordings) that belong together. If the list contains more than `limit` collections, the response will also contain a non-null `cursor` value that can be used to fetch the next page of collections in the list by calling the tool again and passing the `cursor` along with the same `filters`. The list will be empty if there are no collections matching the supplied filters.

list_collections

Returns a filtered list of Grain meetings you have access to, ordered by most recent. If the list contains more than `limit` meetings, the response will also contain a non-null `cursor` value that can be used to fetch the next page of meetings in the list by calling the tool again and passing the `cursor` along with the same `filters`. The list will be empty if there are no meetings matching the supplied filters. If only looking for meetings the user attended, use `list_attended_meetings` instead. Use this when the user asks which meetings happened. For "what did we decide / discuss / know about X" questions, call `recall_meeting_memory` first instead of listing meetings.

list_meetings

Fetches detailed information about a single Grain story by ID, including its items (clips and text sections). Use list_stories first to find story IDs.

fetch_story

Get information about the logged-in Grain user.

myself

Fetches the Company Intelligence dossier for a single company by `company_id` (the id returned by `search_companies`). The dossier is returned as markdown plus metadata. If the company exists but has no dossier generated yet, `markdown` and the metadata fields are null. Read-only: this never triggers dossier generation. Use this for a standing company profile. For what was decided or discussed with the company across meetings, call `recall_meeting_memory` first.

get_dossier_for_company

Get your personal settings. For overrideable settings, a null value means the team (or workspace) setting is being applied. If your team does not allow overrides (`team_settings_overridable` is false), overrideable settings always return null. You can use `update_my_settings` to change these settings.

my_settings

Get the settings of the team you belong to. You can use `my_settings` to see your personal setting overrides.

my_team

Sends email invitations to the specified email addresses to join your Grain workspace. Requires a workspace admin and supports up to 50 email addresses per call. If an address has a pending workspace access request, approves that request instead. Invitations use free seats by default; selecting paid seats can incur charges when invitees join. An optional team assignment applies to a Grain team within the same workspace.

invite_to_workspace

List status of hubspot-linked deals that are synced in Grain. If the list contains more than `limit` deals, the response will also contain a non-null `cursor` value that can be used to fetch the next page of deals in the list by calling the tool again and passing the `cursor` along with the same `filters`. The list will be empty if there are no deals matching the supplied filters.

list_all_deals

List AI-generated sales-coaching feedback and scorecards for a filtered set of meetings. If the list contains more than `limit` meetings, the response will also contain a non-null `cursor` value that can be used to fetch the next page of meetings in the list by calling the tool again and passing the `cursor` along with the same `filters`. The list will be empty if there are no meetings matching the supplied filters.

list_coaching_feedback

List status of open hubspot-linked deals that are synced in Grain. If the list contains more than `limit` deals, the response will also contain a non-null `cursor` value that can be used to fetch the next page of deals in the list by calling the tool again and passing the `cursor` along with the same `filters`. The list will be empty if there are no open deals matching the supplied filters. If also looking to include closed deals, use `list_all_deals` instead.

list_open_deals

Get information about all the users in the logged-in Grain user's workspace. Each user's ID can be used to list recordings attended by that user.

list_workspace_users

Returns a paginated list of Grain clips you have access to, ordered by most recent. Clips are short segments from meeting recordings. If the list contains more than `limit` clips, the response will also contain a non-null `cursor` value that can be used to fetch the next page by calling the tool again. Only returns clips whose media has finished processing, so newly-created clips may take a few minutes to appear.

list_clips

Lists the smart topics configured in your Grain workspace. Smart topics are saved classifiers that mark where meetings discuss a given subject. Use the returned `id` values with the `smart_topics` filter on the meeting-listing tools (e.g. list_meetings) to find meetings matching a topic. Deactivated topics are hidden unless `include_inactive` is true.

list_smart_topics

Returns a paginated list of Grain stories you have access to, ordered by most recent. Stories are curated collections of clips and text sections created from meetings. If the list contains more than `limit` stories, the response will also contain a non-null `cursor` value that can be used to fetch the next page by calling the tool again.

list_stories

Lists team IDs and names in your workspace. Use these IDs in the teams meeting filter.

list_teams

Lists teams and a number of their settings. You can use `update_team_settings` to update these settings.

list_team_settings

Lists a number of settings that affect your entire workspace. Meeting capture and sharing settings are workspace-wide defaults; team settings (`list_team_settings`) and personal overrides (`list_user_settings`) take precedence where set. You can use `update_workspace_settings` to update these settings.

workspace_settings

Lists a few basic information about users and a number of settings. Basic information may not be updated. Settings may be updated using `update_user_settings` For members of teams that disallow overrides (`team_settings_overridable` is false), team settings are always used and user settings are returned as null. For users without a team, a non-null value indicates their effective user setting. To achieve parity among overrideable user settings, prefer setting their team's `team_settings_overridable` to false instead of updating multiple users.

list_user_settings

Moves one or more users into a team. Users already on a different team will have their team changed to the new one.

move_users_to_team

Remove a tag from up to 50 Grain meetings you can access, using their meeting IDs. Detaches the tag from the selected meetings.

remove_tag_from_meetings

Removes a user from a team.

remove_user_from_team

Turns Grain entity IDs into clickable shareable URLs. Call this whenever you are about to show a link to a meeting, clip, collection, or story to the user (for example: "share this meeting", "send me the link", or when citing a source). NEVER build a Grain URL by hand or guess one from an ID — hand-built URLs are almost always wrong. This tool is the only correct way to get a URL. Use each returned URL exactly as given and never append anything to it, such as `|Clip`. To label a link, use Markdown (`[label](url)`) instead of `<url|label>` syntax.

resolve_urls

Returns filtered lists of companies that were participants of Grain meetings you have access to. Use one call with all requested company names when the user asks about multiple companies. Set `limit` low, usually 1-3, when company names are specific. For "what do we know about <company>" or call-prep questions, call `recall_meeting_memory` with the company name first; only resolve a `company_id` here when a filter or `get_dossier_for_company` needs it.

search_companies

Returns contacts in your workspace. Without a search string, returns contacts from your most recent meetings.

search_contacts

Searches transcripts of Grain meetings and returns the matching segments rather than the full transcript. Useful for locating verbatim quotes, specific moments, or raw discussion segments across one or many meetings without loading entire transcripts. Uses hybrid semantic + keyword search over transcript segments — coherent conversation chunks annotated with summaries, topics, entities, and speaker info. Results are grouped by meeting and ordered by relevance. For synthesis questions ("what did we decide about X", "what do customers keep asking for", "what do we know about Y") call `recall_meeting_memory` first; it already synthesizes across meetings. Use this tool when you need the exact words, a specific meeting, or recall reported no memory on the subject.

search_in_transcripts

Removes the paid seat from one or more workspace users. The unassigned seats remain available and can be reassigned at any time until the end of the current billing cycle.

unassign_paid_seat_from_users

Changes the visibility of a collection (also known as a playlist). Options: 'restricted' (only shared users), 'workspace' (all workspace members), 'public' (anyone with the link).

update_collection_share_state

Update your personal settings. Set a field to null to unset your override and fall back to your team's setting. Overrides only take effect when your team allows them (`team_settings_overridable` is true).

update_my_settings

Update team settings

update_team_settings

Update workspace settings

update_workspace_settings

Updates settings for a user. Team settings take precedence for members of teams that disallow overrides (`team_settings_overridable` is false). To achieve parity among overrideable user settings, prefer setting their team's `team_settings_overridable` to false instead of updating multiple users.

update_user_settings