List the automations on the signed-in person's account — saved chains of steps they built in the web app to run over a finished transcript. Read-only, and there is deliberately no tool here that creates or edits one. Requires an OAuth 2.1 user access token.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey read-only, idempotent, non-destructive behavior. The description adds real value beyond those annotations by specifying the OAuth 2.1 user access token requirement and the 'signed-in person's account' scope, which are not expressed in the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three tight, purposeful sentences. The core action is front-loaded, the definition of automations earns its place, and the read-only/no-create note plus auth requirement are each materially useful without adding clutter.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only list tool with rich annotations, this description is complete: it defines the resource, scope, auth requirement, and side-effect profile. No output schema exists, but 'List the automations' sufficiently implies the returned content.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters and the schema is empty, so the baseline for parameter semantics is 4. The description correctly adds no parameter details that would be redundant with the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List') and resource ('automations on the signed-in person's account'), and defines what an automation is ('saved chains of steps'). This distinguishes it from sibling tools like run_automation and get_automation_run without needing to open their schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context: it is read-only and scoped to the signed-in person's automations. It also explicitly notes that no create/edit counterpart exists, preventing an agent from searching for one, though it doesn't explicitly name alternative tools like run_automation for execution use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The set contains several near-neighbor groups: deprecated aliases duplicate live tools, and docs/billing/financial tools have fuzzy boundaries. Individual descriptions are detailed and resolve most collisions, but matching the right tool among 39 still requires care.
Most tools follow a sensible verb_object style, but the transcribe_* group is inconsistent: transcribe_url/transcribe_upload are verb_object, while transcribe_status/transcribe_cancel/transcribe_delete are really status/cancel/delete operations renamed with a transcribe prefix. The deprecated transcription_status/transcription_url aliases add another naming convention, so the pattern is not reliable across the set.
39 tools is well over the 25+ threshold and creates an overwhelmingly broad surface spanning account management, billing, docs, API jobs, library organization, meeting bots, and automations. Two deprecated duplicates inflate the count further. This would be more coherent split into separate servers or at least pruned of deprecated aliases.
Core API transcription lifecycle is covered, and the library/meeting-bot flows have search, tagging, moving, and audio retrieval. However, there is no user-library deletion/rename, no OAuth-side full-transcript access, local upload is non-functional over the hosted endpoint, and webhook management is documented but not exposed as tools. These gaps force agents to work around missing operations.
