Streak

Get detailed information about a box by its key. Use this when: you have a box key and need detailed information such as custom field values, notes, magic columns, or linked contacts/organizations. Do not use for: searching boxes (use search or filter_boxes).

get_box

Return the latest stored AI summary for a box by its key. Use this when: the user asks for the existing full AI summary, next steps, or concise digest of a specific box. This does not generate a new summary or consume AI summary credits. To create or refresh a summary, use regenerate_box_summary.

get_box_summary

Get all tasks on a specific box by box key. Returned taskKey values can be passed to update_task. Use this when: the user asks for tasks/reminders/followups on a specific box, or you need a task key before updating a task in a known box. PREREQUISITE: Use a box key returned by search, filter_boxes, get_recent_boxes, create_box, get_box, or fetch. Do not use for: creating tasks (use create_task), updating tasks (use update_task), or listing upcoming tasks across boxes (use get_upcoming_tasks).

get_box_tasks

Get detailed information about a contact by its key. Use this when: you have a specific contact key. Do not use for: searching contacts (use search).

get_contact

Use this when you need detailed information about a specific pipeline, including its stages, custom fields/columns, saved views, and users with access. Saved view keys can be passed to get_saved_view_boxes. Do not use for: listing all pipelines (use list_pipelines) or searching by name (use search).

get_pipeline

PRIORITY TOOL: Check this first when users mention boxes without specific criteria. Get boxes recently viewed by the current user. Use this when: user asks about recent boxes, 'what was I working on', or refers to a box without specifying its name. Missing (call get_box for): custom field values, notes, email/task counts, linked contacts/organizations. Do not use for: searching by name (use search) or filtering by criteria (use filter_boxes).

get_recent_boxes

Get boxes from an existing saved view using its saved view key. Applies the saved view's persisted filters, sorts, and grouping. PREREQUISITE: Use get_pipeline or search to find a saved view key. Use this when: the user asks for boxes in a named saved view or provides a saved view key. Do not use for: ad hoc filtering criteria (use filter_boxes) or a single box lookup (use get_box).

get_saved_view_boxes

Gets upcoming and overdue tasks assigned to the current user, including overdue tasks and tasks without a due date. Returns up to 50 tasks, with undated tasks first and dated tasks ordered by due date, oldest first. Optionally limit results to a single pipeline. Use this when: the user asks what tasks are coming up, what reminders they have, or what they need to work on next. Do not use for: creating tasks (use create_task) or looking up all tasks on a specific box (use get_box_tasks).

get_upcoming_tasks

Get information about the authenticated user including name, email, time zone, and current date/time. Use this when: personalizing responses or needing user context. Do not use for: finding other users.

get_current_user

List all pipelines the current user has access to. Use this when: discovering available pipelines or when the user asks to see their pipelines/CRMs. IMPORTANT: This returns stage/field COUNTS only, NOT actual names/keys. If you need stage keys, field names, or user list, you must call get_pipeline first. Do not use for: getting pipeline details (use get_pipeline) or finding boxes (use filter_boxes).

list_pipelines

Generate and return a fresh AI summary for a box by its key. Use this when: the user explicitly asks to generate, regenerate, refresh, or update a box summary. This persists the new summary to the box and consumes AI summary credits. To read the existing full summary without generating a new one, use get_box_summary. For existing generated short summaries, use get_box, fetch, filter_boxes, or get_recent_boxes.

regenerate_box_summary

Search across Streak boxes, contacts, organizations, pipelines and saved views by keyword. Use this when: finding items by name or text content. Do not use for: filtering by criteria (use filter_boxes) or getting recent boxes (use get_recent_boxes).

search

Send feedback to Streak when you wanted to do something through the Streak MCP or API, but no available tool supports it. Use this whenever a Streak MCP/API capability is missing. Provide the desired tool or capability and the high-level user goal. This feedback is very valuable because it helps Streak add the right MCP tools soon. Do not include sensitive or personal information, customer data, email addresses, names, message contents, or Streak record keys. Summarize the missing capability instead.

feedback

Update a box's name, notes, stage, assignees, and/or custom field values in a single call. Use this when: editing a box's title, changing its notes, moving it to a different stage, assigning or reassigning users, or setting custom field values such as a dropdown, tag, checkbox, date, text, or contact/organization field. PREREQUISITE: Call get_pipeline to discover stage keys, custom field keys and types, dropdown/tag option keys (use the 'key' property), and users with access for assignment. Stage and dropdown/tag values may be passed as the key or the display name. Provide at least one of name, notes, stageKey, assignedTo, or fields. Pass an empty string for notes to clear them, or for assignedTo to unassign all users. For dropdown/tag fields, prefer an existing option key or name from get_pipeline. Passing an unknown value silently creates a new option on the pipeline field, so avoid typos and casing variants. When that happens the returned field value is a new option key you have not seen — re-fetch get_pipeline to refresh your cached option list and tell the user a new option was created. Do not use for: creating boxes (use create_box) or reading box details (use get_box). For a single focused change, assign_box and update_box_stage are alternatives.

update_box

Move a box to a different stage in its pipeline. PREREQUISITE: Call get_pipeline first to discover available stage keys (use 'key' property, not 'name'). Use this when: updating deal status, moving to next stage, or changing workflow state. Do not use for: getting box details (use get_box) or other box modifications.

update_box_stage

Update a task's text, due date, completion status, and/or assignees in a single call. Use this when: editing a task/reminder/followup, marking a task done or not done, changing its due date, clearing its due date, assigning it to users, or unassigning all users. PREREQUISITE: Use task keys returned by create_task, get_upcoming_tasks, or get_box_tasks. Assigned users must be provided as email addresses with access to the task's pipeline. Provide at least one of text, dueDate, status, or assignedTo. Pass an empty string for dueDate to clear it, or for assignedTo to unassign all users. Do not use for: creating tasks (use create_task) or reading upcoming tasks (use get_upcoming_tasks).

update_task