Back to tracker
Plugin tracker
Tools
Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.
Latest snapshot2026-09-13USmethodology registry-public-v1
Searchable tools
119,491
Authless tools
7,773
Auth required
107,252
Described tools
64,388
119,491 tools
- Get Q&A Statusgetqastatus · Get Q&A information for a Datasite project. Returns either:
- A specific question with all posts and answers (when questionId is provided)
- An overview with question listing, summary dashboard, and visible categories (when questionId is omitted)
Category visibility is access-filtered. If a requested category is not returned, tell the user it may either not exist or may not be accessible to them; do not state that it definitely does not exist.
Use manageQuestion for creating or updating questions.
If a question has status IN_PROGRESS, it cannot be answered further, as it is still in draft and only one draft can exist at a time.DatasiteDatasite
PluginrequiredFinance - Grant Feature Accessgrantfeatureaccess · Grant a role-level feature access permission in a Datasite project.
This controls which roles can access specific project features (e.g. Q&A, bulk download) — it does not activate paid product features like AI-powered content search.
Use getAccessControl(scope=PROJECT, includeFeatureAccesses=true) to discover available keys.DatasiteDatasitePluginrequiredFinance
- Invite Userinviteuser · Invite a user to a Datasite project by email address and assign them a role. Use only for an email address that is not yet a member of the project.
This tool does not change or reassign the role of an existing member, and it does not modify any existing membership. Calling it for someone who is already a member will send them another invitation email.
Specify the role by name (e.g., "Reviewer") or by roleId; roleName is resolved automatically.DatasiteDatasitePluginrequiredFinance
- List Folder Contentslistfoldercontents · List the contents of filerooms and folders in a Datasite project. Returns item metadata — names, IDs, types (FILEROOM, FOLDER, DOCUMENT, PLACEHOLDER, SANDBOX), statuses, file types, and publishing states — but NOT document text.
Use this to navigate the folder tree, see what documents exist and their metadata, or find where content is located before creating, uploading, or modifying it.
To find information inside documents (e.g. clauses, risks, or specific content), use searchDocuments instead.
Behavior by parameters:
- No metadataId: Returns the top-level fileroom listing with IDs.
- With metadataId: Returns contents under that folder or fileroom. depth controls how much of that folder to list.
- depth (default 1, max 5): Controls how many levels deep to traverse. depth=1 returns immediate children only. depth > 1 follows folder contents breadth-first, returning all items with depth and path columns so you can understand the visible structure in one call instead of browsing level by level. Must be between 1 and 5.
- foldersOnly (default true): When true, only folder-type items (FILEROOM, FOLDER, SANDBOX, INBOX) are returned. Set to false to include documents in the results. Applies at all depth levels.
- limit: Maximum matching direct children to fetch for each folder that is read. Defaults to 1,000. Must be between 1 and 1,000.
- skip: Number of matching direct children to skip before returning results. Defaults to 0. Must be 0 or greater. Only valid with depth=1. Use a returned node's listingStatus.nextCall to continue reading that specific folder.
Nodes omit listingStatus when there is nothing else to do. A returned listingStatus means the node's folder listing is incomplete or needs attention. NOT_READ means contents were not read, usually because depth stopped there or a fetch failed. PARTIAL means more direct children are available and listingStatus.nextCall gives the next listFolderContents call.
The listing may include items with type SANDBOX (named "Staging Folder"). A sandbox is a staging area
where content is uploaded before being published to regular filerooms.
PREPARE projects use the sandbox exclusively for uploads — all content must go through the Staging Folder.DatasiteDatasitePluginrequiredFinance
- List Projectslistprojects · List all Datasite projects you have access to, optionally enriched with subscription context.
Use this to find projects by name, ID, state, or to discover which subscription a project belongs to.
Set includeSubscriptionInfo=true to include subscription details.DatasiteDatasitePluginrequiredFinance
- List Subscriptionslistsubscriptions · List all Datasite subscriptions you have access to. Returns subscription name, ID,
and allowed offering types. Use this to find which subscription to use when creating a new project.DatasiteDatasitePluginrequiredFinance
- Manage Questionmanagequestion · Create Q&A question drafts, update questions, or categorize Q&A questions in a Datasite project.
This is the default tool for creating question drafts when the current user is not on an ANSWER team. Use submitQuestionOnBehalf only after getMyQandaTeam confirms the current user is on an active ANSWER team.
action=CREATE: creates an IN_PROGRESS draft only for the caller's QUESTION team; requires categoryId, gateId, and workflowIndex.
RULES FOR CREATE:
- Call getQandaGateContext first to confirm what gates the user is a part of, and therefore, what categories they can submit questions for.
- assignedToIds may contain only users from gateMemberUserIds returned by getQandaGateContext. Omit it to assign every gate member.
- If the user requests to assign no other users to the question, pass an empty array into the assignedToIds parameter. Else, omitting it will assign every gate member.
- Use getMyQandaTeam to identify the current user's Q&A team, and getQAStatus with includeCategories=true to list visible categories. If a requested category is not returned, tell the user it may either not exist or may not be accessible to them; do not state that it definitely does not exist. The question is not submitted.
- Ideally, before creation, notify the user of the fact that questions will be created as draft.
- Once a question is created as a draft, provide the user with a URL to go to the UI to view the draft.
- If the user mentions that they want to attach documents to the question, the listFolderContents should be called to list the available documents BEFORE creating the question. DocumentIds need to be passed into the tool to properly attach the documents.
- DO NOT ATTEMPT TO CREATE A QUESTION DRAFT IF THE USER IS NOT IN THE GATE.
action=UPDATE: requires questionId and closed. Supports closing/reopening via the closed param.
action=CREATE_CATEGORY: requires categoryName.DatasiteDatasitePluginrequiredFinance
- Manage Rolemanagerole · Create or update a role in a Datasite project.
action=CREATE: requires name. action=UPDATE: requires roleId, optional name to rename.DatasiteDatasitePluginrequiredFinance
- Move Contentmovecontent · Move files or folders to a different location within a Datasite project.
This is a destructive operation. User confirmation is recommended before execution.
When moving a folder, all children are moved automatically.
Moved items keep their current permissions and publishing status.
Each result includes a url to review the moved item at its new location.
Supports moving up to 100 total items (including all children) for synchronous moves.
If bulk move is enabled, moves exceeding 100 items are processed asynchronously and return an operation ID.DatasiteDatasitePluginrequiredFinance
- Search Documentssearchdocuments · Search across document content in a Datasite project using AI-powered semantic search. Applies to Diligence and Acquire projects.
Returns matching text passages from inside documents with relevance scores, page numbers, and source paths.
Each result includes a url (when the source document is identifiable) that opens the source document and highlights the matched passage — when citing information from a result, always use that result's url as the citation link, never a project-level or homepage URL from other tools.
Use this whenever you need to find information, clauses, risks, or answers within documents — not for navigating folder structure.
Blueflame search is only available for eligible users on Diligence and Acquire projects. If the project type is unsupported or the user does not have access, this tool returns structured, actionable guidance instead of results. Not all users can self-activate Blueflame; the guidance reflects the appropriate next step for the user's role and project.
Limit caps at 25. Set rerank=true to rerank results by relevance at the cost of higher latency.DatasiteDatasitePluginrequiredFinance
- Search Help Docssearchhelpdocs · When to use:
Customer-facing help centre articles explaining how Datasite features work — e.g. "how do I create a tracker," "what is a fileroom,"
"why can't I invite this user," "what does this setting do." Does NOT search content inside a customer's project or data room — use searchDocuments for that.
What this tool returns:
A list of scored passages, ordered by relevance (highest first). Each result includes: score, matching_text (the actual passage content — use this
for your answer), source_url, article_id, title, and section. article_id, title and section are sometimes blank or missing (older indexed passages) — still cite
the source_url when this happens. Lower-scoring results may be less relevant; don't treat all returned results as equally authoritative.
Response requirements:
Attach source_url close to the claim it supports, rather than batching all citations at the end of the response.
Name the article title and section alongside each citation when available.
Never restate help content without a citation.
If no results are returned, tell the user no help article matched. Do not fall back on your own knowledge of Datasite.
If results are returned but none are actually relevant to the query (check scores and content, not just presence of results), tell the user no relevant help article was
found — do not stretch a low-relevance passage to fit the question.
Before sending your response, confirm every claim has a source_url attached, or revise.DatasiteDatasitePluginrequiredFinance
- Setup Projectsetupproject · Create a new Datasite project and optionally set up its initial content structure in one call.
IMPORTANT — CONFIRM REQUIRED FIELDS BEFORE CALLING:
- datacenter is always an explicit user choice. If the user has not stated a region, STOP and ask before
calling this tool. Do not infer datacenter from the user's apparent location, the project name, the
conversation topic, or prior projects. This is a data-residency decision with compliance implications —
never default to USA (or any other region) just because it is listed first or seems likely.
- useCase, industryType, and transactionValue should come from the user's description of the deal. If the
user has given enough freeform context to map confidently to the enum values, you may do so. If not,
ask a short clarifying question first. Do not fabricate values that are unsupported by what the user has
actually said.
One round-trip to confirm is always cheaper than creating a project with wrong metadata.
SUBSCRIPTION: subscriptionId is optional only in limited cases. Omitting it works when the user has no
enterprise subscriptions — the service will resolve their default usage subscription automatically. If the
user may belong to an enterprise account or have access to multiple subscriptions, call listSubscriptions
first and ask them which to use, then pass its ID as subscriptionId. If a create call without
subscriptionId fails because a subscription is required, fall back to listSubscriptions and ask the user
to pick one.
A Staging Folder (sandbox) is automatically created for the project. If contentPaths is provided,
paths default to folders inside the sandbox unless an explicit type override is provided.
contentPaths is a flat JSON array where each entry is a full path string plus optional type and published flag:
- path (required): Full slash-separated path, e.g. "/Financial/Q1" or "/Legal"
- type (optional): Override type for the final segment of this path — FILEROOM or FOLDER (auto-inferred if omitted)
- published (optional): Whether the final segment of this path is visible to non-admin users (defaults to false). Not applicable in PREPARE projects — publishing is not supported.
Shared ancestor segments are deduplicated automatically. To set type on an ancestor, list it as its own entry alongside its children (e.g. {"path":"/Financial","type":"FILEROOM"} and {"path":"/Financial/Q1"}).
Example: [{"path":"/Financial/Q1"},{"path":"/Financial/Q2"},{"path":"/Legal"}]
Do not prefix fileroom or folder names with numbers or numeric sequences (e.g. "01.", "1.", "1 -"). Use plain descriptive names only.
Do not suggest publishing content for PREPARE projects — publishing is not a supported feature in PREPARE.DatasiteDatasitePluginrequiredFinance
- Submit Question On Behalfsubmitquestiononbehalf · Submit one or more Q&A questions on behalf of a question team from an answer-team admin context.
- BEFORE using this tool, call getMyQandaTeam for the project. Use submitQuestionOnBehalf only when getMyQandaTeam returns onQandaTeam=true, teamType=ANSWER, active=true, and allowedToSubmit=true.
- If getMyQandaTeam shows the current user is not on an active ANSWER team, do not use submitQuestionOnBehalf.
- If getMyQandaTeam shows the current user is in the QUESTION team, use manageQuestion for question-team draft creation instead.
- If the user mentions that they want to attach documents to the questions, the listFolderContents should be called to list the available documents BEFORE creating the questions. Each question has it's own documentIds collection that is there to express what documents the user wants to link to each question.
- Use getMyQandaTeam to confirm the current user's team context, and getQAStatus with includeCategories=true to find visible category names and ids. If a requested category is not returned, tell the user it may either not exist or may not be accessible to them; do not state that it definitely does not exist.
- Use getQAStatus to get data about the question teams currently configured in the Q&A enabled project.
- Use getQandaGateContext to find the correct gate/workflow information for the respective category in the question team.
- Questions must be supplied through the questions array, even when importing a single question.
- Imported questions are created as in-progress question-team drafts assigned to the first gate members.
- User must be notified that the question will be created as a draft and will be assigned to all team members in the corresponding question team workflow, based on category.
- It is possible you will be extracting text from an Excel file. If so, make sure the question content is left totally unchanged -- do not modify it in any way unless requested to do so.
- Do not provide the user with any URLs to look at the questions in the platform/UI once they have been posted. Since they're submitted as drafts, they become visible to question team members only.
- After the questions are created, let the user know they're saved as drafts and won't be visible to any answer team member—including the user—until the question team submits themDatasiteDatasitePluginrequiredFinance
- Update Contentupdatecontent · Update a document or folder in a Datasite project. Supports renaming, and supports changing publishing status only for non-PREPARE projects.
Identify the item by metadataId or human-readable path (e.g., "Financial/Q1 Reports").
Do not suggest publishing status changes for PREPARE projects — publishing is not a supported feature in PREPARE.DatasiteDatasitePluginrequiredFinance
- Update Membershipupdatemembership · Activate or deactivate a user's membership in a Datasite project.
Use getMembers to find user IDs. Status must be ACTIVATED or DEACTIVATED.DatasiteDatasitePluginrequiredFinance
- Update Permissionsupdatepermissions · Get a link to manage content permissions for a Datasite project via the web application.
Optionally provide a fileroom or folder ID to navigate directly to its permissions page.
Returns a browser URL where the user can review and update permissions manually.DatasiteDatasitePluginrequiredFinance
- Upload Contentuploadcontent · Get a link to upload documents to a Datasite project via the web application.
Specify the destination as a human-readable path (e.g., "Financial/Q1 Reports") or a direct folder ID.
Returns a browser URL that opens the target folder in the Datasite web application, where the user can complete the upload.
For PREPARE projects, uploads must target the Staging Folder (sandbox). Browse content first to find
the sandbox, then use its path or ID as the destination.DatasiteDatasitePluginrequiredFinance
- Add Call Log or Meeting Notesadd · Create a call log or meeting notes entry on a Streak box. Use this when: logging a phone call, recording a meeting, or adding meeting notes to a box in a pipeline. Set meetingType to CALL_LOG for calls or MEETING_NOTES for meetings. Both support notes, duration, and a start timestamp. If the user names a box or pipeline, find the box first and pass its boxKey. This creates an activity entry; it does not change the box's Notes field or schedule a calendar event. Do not use for: viewing call or meeting history.StreakStreakPluginrequiredSales & CRM
- Add Thread To Boxadd · Add a Gmail thread to a box.
PREREQUISITE: You need a box key and a Gmail thread id. Use search, filter_boxes, get_recent_boxes, or get_box
to find a box key first.
Use this when: associating an existing Gmail conversation with a specific Streak box.StreakStreakPluginrequiredSales & CRM
- Assign Boxassign · Assign a box to users by email address, or unassign all users by passing an empty string. Use this when: assigning, reassigning, or unassigning a box. Do not use for: viewing box details (use get_box).StreakStreakPluginrequiredSales & CRM
- Create Boxcreate · Create a new box in a pipeline with optional stage and assignment.
Use this when: creating a new deal, lead, case, project, ticket, or other pipeline row in Streak.
PREREQUISITE: Use list_pipelines to discover pipeline keys. If setting a stage or assigning teammates, call get_pipeline first to discover stage keys and users with access.
The box name and pipeline key are required.
The stage defaults to the first stage in the pipeline. Use stage keys, not stage names.
The assignee defaults to the current user. Use comma separated email addresses for multiple assignees.
Do not use for: updating existing boxes (use update_box_stage or assign_box) or searching boxes (use search or filter_boxes).StreakStreakPluginrequiredSales & CRM
- Create Commentcreate · Create a new top-level comment on a box. Supports @mentions for users who already have access to the box.
PREREQUISITE: You need a box key. Use search, filter_boxes, get_recent_boxes, or get_box to find one first.
To mention someone, include @name, @email, or @email-local-part in the message.
Do not use for: replying to an existing comment. Replies are not supported by this tool because the current MCP surface does not provide a way to select an existing comment as a reply target.StreakStreakPluginrequiredSales & CRM
- Create Contactcreate · Create a team contact and link it to a box, or update/return the matching existing contact when one already matches by email or name.
Use this when: adding a person to a specific Streak box.
Provide boxKey and at least one of givenName, familyName, or emailAddresses for the contact.
Set include_all_emails to true to automatically pull in on all the emails with this contact into the box.StreakStreakPluginrequiredSales & CRM
- Create Organizationcreate · Create a team organization and link it to a box, or return the matching existing organization when getIfExisting is true and a domain already exists.
Use this when: adding a company/account to a specific Streak box.
The box determines which team owns the organization. Provide boxKey and at least one of name or domains.
Set include_all_emails to true to include all team emails with that organization in the box.StreakStreakPluginrequiredSales & CRM
- Create Taskcreate · Create a new task in a box with optional due date and assignment. Useful for setting reminders and tracking follow-ups. Use this when: adding a task, setting a reminder, or tracking something to do for a box. Do not use for: viewing existing tasks.StreakStreakPluginrequiredSales & CRM
- Fetch Streak Datafetch · Get complete details for an item found via search. Required for Deep Research mode. Takes a search result ID returned by search and returns full content. Use this when: you performed a search and need detailed information. To get boxes from a saved view result, use get_saved_view_boxes. Do not use for: direct lookups by key (use get_box, get_contact, or get_pipeline).StreakStreakPluginrequiredSales & CRM
- Filter Boxesfilter · Filter boxes in a pipeline with structured filters and sorting.
PREREQUISITE: Call get_pipeline first to discover stage keys, field names, dropdown/tag options, and users.
IMPORTANT: Most queries need 2+ filters. Identify ALL criteria in the query.
Example: "my active deals" needs: [{ field: "assignedTo", operator: "equals", value: "me" }, { field: "stageKey", operator: "equals", value: "Active" }]
Example: "boxes in Scheduled stage for Cooldown sprint" needs: stageKey filter + Sprint filter
SYSTEM FIELDS (primary filters - check these first):
stageKey (workflow stage), assignedTo (owner), createdBy, creationTimestamp, lastUpdatedTimestamp, lastStageChangeTimestamp, name, notes
OPERATORS BY FIELD TYPE:
TEXT (name, notes, custom text fields):
- 'contains'/'not_contains': substring search
- 'equals'/'not_equals': exact match
- 'is_set'/'is_not_set': check if has value
Example: { field: "name", operator: "contains", value: "Acme" }
DATE (creationTimestamp, lastUpdatedTimestamp, custom date fields):
- 'greater_than'/'less_than': compare dates (ISO-8601 UTC)
- 'equals': exact date match
- 'is_set'/'is_not_set': check if date is set
Example: { field: "creationTimestamp", operator: "greater_than", value: "2025-01-15T10:30:00Z" }
NUMBER (taskTotal, totalNumberOfEmails):
- 'greater_than'/'less_than': numeric comparison
- 'equals'/'not_equals': exact value
Example: { field: "taskTotal", operator: "greater_than", value: "5" }
DROPDOWN (stageKey, custom dropdown fields):
- 'equals'/'not_equals': match by name or key
- 'is_set'/'is_not_set': check if selected
Example: { field: "stageKey", operator: "equals", value: "5001" }
TAG (custom tag fields):
- 'includes': has ANY of specified tags (use 'values', not 'value')
- 'excludes': has NONE of specified tags
- 'is_set'/'is_not_set': check if any tags
Example: { field: "Tags", operator: "includes", values: ["9001", "9002"] }
USER (assignedTo, createdBy, followers, taskAssignees, incompleteTaskAssignees, overdueTaskAssignees, custom person fields):
- 'includes': specific user(s) by email (use 'values')
- 'excludes': exclude specific user(s)
- 'contains': partial name/email text search (use 'value')
- 'equals': single user match or "me" for current user
- 'is_set'/'is_not_set': check if assigned
Example (by email): { field: "assignedTo", operator: "includes", values: ["user@example.com"] }
Example (custom person): { field: "Account Manager", operator: "includes", values: ["manager@example.com"] }
CHECKBOX (custom checkbox fields):
- 'is_set': checkbox is checked (true)
- 'is_not_set': checkbox is unchecked (false)
Example: { field: "Approved", operator: "is_set" }
SORTING: sorts: [{ field: "lastUpdatedTimestamp", direction: "desc" }]
All filters combined with AND. Do not use for: an existing saved view (use get_saved_view_boxes), keyword search (use search), or a single box lookup (use get_box).StreakStreakPluginrequiredSales & CRM
- Get Boxget · 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).StreakStreakPluginrequiredSales & CRM
- Get Box Summaryget · 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.StreakStreakPluginrequiredSales & CRM
- Get Box Tasksget · 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).StreakStreakPluginrequiredSales & CRM
- Get Contactget · 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 or search_contacts).StreakStreakPluginrequiredSales & CRM
- Get Pipelineget · 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).StreakStreakPluginrequiredSales & CRM
- Get Recent Boxesget · 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).StreakStreakPluginrequiredSales & CRM
- Get Saved View Boxesget · 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).StreakStreakPluginrequiredSales & CRM
- Get Upcoming Tasksget · Get upcoming incomplete tasks assigned to the current user. 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 fetch/get_box as needed).StreakStreakPluginrequiredSales & CRM
- Get authenticated user detailsget · 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.StreakStreakPluginrequiredSales & CRM
- List Pipelineslist · 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).StreakStreakPluginrequiredSales & CRM
- Regenerate Box Summaryregenerate · 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.StreakStreakPluginrequiredSales & CRM
- Search Streak Datasearch · 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).StreakStreakPluginrequiredSales & CRM
- Send Feedbackfeedback · 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.StreakStreakPluginrequiredSales & CRM
- Update Boxupdate · 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.StreakStreakPluginrequiredSales & CRM
- Update Box Stageupdate · 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.StreakStreakPluginrequiredSales & CRM
- Update Taskupdate · 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).StreakStreakPluginrequiredSales & CRM
- Compare family hotelscompare · Compare 2–4 family stays side by side as SplashScout cards, with age scores and features. Accepts ids or names.SplashScoutSplashScoutPluginnoneTravel & Hospitality
- Get a curated guideget · SplashScout's curated, ranked 'Best family hotels/campsites in [destination]' guides — overall, or focused on toddlers, kids, teens, water slides or splash parks. Prefer this over search for 'best X in Y' questions: it returns our editorial ranking as interactive cards plus a link to the full guide. E.g. 'best family hotels in Turkey with splash parks' → destination 'Turkey', focus 'splash'.SplashScoutSplashScoutPluginnoneTravel & Hospitality
- Get a family hotelget · Show a detailed SplashScout card for one hotel/campsite (age scores, features, our in-person review). Accepts an id or a name.SplashScoutSplashScoutPluginnoneTravel & Hospitality
- Search family hotelssearch · Find kid-friendly hotels & campsites with pools, slides and splash parks, scored for toddlers, kids and teens. Returns interactive SplashScout cards plus a text summary. Use for prompts like 'best family hotel in Tenerife for a toddler' or 'campsites in France with big slides'.SplashScoutSplashScoutPluginnoneTravel & Hospitality
- contact_windsorcontact · Windsor.ai: Send feedback, a support request, or a feature request.
Reports a problem, shares feedback, or suggests a feature. Inquiries are
recorded in English. Returns a reference ID the user can share with
Windsor.ai support.Windsor.ai TikTok AdsWindsorPluginrequiredData & Analytics
- create_custom_fieldcreate · Windsor.ai: Create a custom (formula) field on a connector.
A custom field is a user-defined metric or dimension computed from a
connector's existing fields; once created it behaves like a normal field in
get_fields, get_data and scheduled exports. Useful for recreating
calculated fields when migrating from another platform.
Call get_fields first for the connector's valid source field ids, and
get_custom_fields to avoid creating a duplicate. This stores configuration
in the user's Windsor.ai account — confirm the field with the user before
creating it.Windsor.ai TikTok AdsWindsorPluginrequiredData & Analytics
- create_destination_taskcreate · Windsor.ai: Create a scheduled export of connector data to a destination.
Call get_destinations and get_destination_setup_info first for the
destination_type, its target fields and a credential_id, and get_fields
for the source field ids.
This creates recurring external state — confirm the source, destination
target, and schedule with the user before calling. Only works when the
destination's create_in_chat is true; otherwise use its setup_url. Never put
secrets in config; the user enters those in the dashboard form.Windsor.ai TikTok AdsWindsorPluginrequiredData & Analytics
What is Tool Explorer?
Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.
How do category and verb filters work?
Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.
Why do auth requirements matter?
Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.