Skip to main content
Glama

seodraft

by app.seodraft
OverviewDiscussionsAdmin

Research topic SERP

research_topic
Destructive

Build a citability brief for one question: People Also Ask, related queries, cited domains, and an AI Overview check. The SERP is always requested with the AI Overview load, so aiOverviewRequested: true with aiOverview: false means Google serves none for this query, not that we did not look. Costs the user about USD 0.004 (one SERP including the AI Overview load) when the topic already has measured metrics, or about USD 0.116 when it must be measured first. A brief built in the last 14 days is returned from storage for free. refreshMetrics re-measures volume (about USD 0.11 extra); refresh_metrics covers more than one term. The whole call is priced and approved as one plan, so it can come back degraded with reason spend-limit before any request: nothing is charged and no brief is stored. It also refuses with reason archived-topic before estimating any cost when the topic is retired; re-adding the term brings it back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes
workspaceIdNoThe workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.
refreshMetricsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
+  "description": "The workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark destructive/open-world/non-idempotent, but description adds pricing, plan approval, spend-limit degradation with no charge/no storage, archived-topic refusal, 14-day cache, and AI Overview semantics. Rich beyond structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose, then layers cost, caching, and failure behavior without filler. Length is justified by the number of non-obvious operational traits.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Includes brief contents, cost model, caching, failure reasons, and AI Overview interpretation. With no output schema, this gives the agent enough to call and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

WorkspaceId is documented in schema; description explains refreshMetrics' cost/effect and frames term as one question. With 33% schema coverage, it compensates for two of three parameters, though term format isn't specified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb 'Build' and resource 'citability brief', and enumerates the brief's contents. The final clause 'refresh_metrics covers more than one term' implicitly distinguishes this single-question tool from the sibling bulk tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly describes cost contexts, free cached briefs, refreshMetrics behavior, and degraded/refusal states. It does not explicitly state when to choose this tool over refresh_metrics, only that refresh_metrics handles more than one term.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All seodraft toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources