Teddit

A prompt and its answers

get_prompt

Read-onlyIdempotent

Get one tracked question in full: each assistant’s verdict, place and tone, the week-by-week history, the third-party pages cited where a competitor was named instead, and one assistant’s latest answer word for word with the competitors it named, the pages it read (yours, third-party, competitors’, reference), with whether each third-party page names the brand once read (by the same rules as the answers), whether it links to the site and the competitors on it and when the site’s assistants first cited it, which one and for which question, and the web searches it ran. Use it after list_prompts to see why a question is won or lost.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "promptId": "<promptId>"
    },
    "name": "get_prompt"
  }
}

Input Schema

Name	Required	Description
`engine`	No	Which assistant’s answer to include (google_aio = Google AI Overviews, google_ai_mode = Google AI Mode). Default: the first that answered.
`promptId`	Yes	The prompt id, from list_prompts.
`projectId`	Yes	The project id, from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description earns credit for disclosing the shape of the payload: per-assistant verdicts, week-by-week history, cited third-party pages, and that only ONE assistant's latest answer is returned verbatim, plus the rule that third-party pages are judged "by the same rules as the answers". It does not state response size limits or whether history is truncated.

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

Conciseness3/5

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

Everything stated is substantive rather than filler, but it is delivered as one ~120-word run-on sentence with deeply nested clauses, so the essential fact (one prompt, one assistant's verbatim answer, full citation history) is buried mid-sentence. Splitting into a purpose sentence and a returns sentence would make it far more scannable.

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

Completeness4/5

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

With no output schema, the description must carry the return-value burden, and it does so thoroughly for a complex read tool: answers, rankings, tone, history, citations, link presence, first-citation attribution, and web searches. Gaps are minor, such as error behavior for an invalid promptId or how much history is returned.

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

Parameters3/5

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

Schema coverage is 100% and the engine enum is fully documented in the schema, including the aliases for Google AI Overviews/AI Mode and the 'first that answered' default, so the description adds nothing beyond it. It only implies promptId provenance via the list_prompts reference. Baseline 3 is appropriate when the schema does the work.

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?

"Get one tracked question in full" gives a specific verb plus resource, and the description immediately distinguishes it from the sibling list tool by positioning it as the deep-dive counterpart to list_prompts. An agent can tell this apart from get_dashboard or get_trends without opening the schema.

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?

"Use it after list_prompts to see why a question is won or lost" states the sequencing prerequisite and the diagnostic intent, which is exactly the context an agent needs. It stops short of naming when NOT to use it (e.g., for aggregate views across many prompts) or any cost/latency exclusions.

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

All Teddit tools Inspect

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

Need Help?