get_evergreen_queueRetrieve an Intelligent Evergreen queue by its ID to return its caption variants, so you can review or reuse recurring social content before scheduling.
Get one Intelligent Evergreen queue including its caption variants.
| Name | Required | Description | Default |
|---|---|---|---|
| queueId | Yes |
Changes observed during successful MCP inspections.
v0.3.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds one useful piece of behavioral context beyond that: the response includes caption variants. It does not address error behavior for an invalid queueId, and no output schema exists to compensate.
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?
A single, front-loaded sentence with zero filler; the key scope qualifier ('one') and the return-content hint ('including its caption variants') are both delivered efficiently.
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 minimal read-only getter with one parameter and no output schema, the description is adequate but thin. It omits how to source the queueId and what happens on failure, leaving the agent to infer the workflow from sibling tools.
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?
Schema description coverage is 0% – queueId is documented only as a bare string with no description. The description never mentions queueId, its expected format, or where to obtain it, so it fails to compensate for the schema gap on the tool's only (required) parameter.
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 (get) and resource (Intelligent Evergreen queue) and scopes it to a single item ('one'), implicitly distinguishing it from the sibling list_evergreen_queues. The sibling is not named explicitly, but the singular framing makes retrieval vs. listing unambiguous.
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?
Usage is only implied: 'one' signals this is a single-item lookup as opposed to the list tool, but there is no explicit when-to-use statement, no note that a queueId must first come from list_evergreen_queues, and no mention of alternatives like preview_evergreen_queue or list_evergreen_runs.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.