MentionForge

Get a frozen research snapshot

get_example

Read-onlyIdempotent

Retrieve a frozen research snapshot for testing without hitting live sources or consuming trial credits. Choose full or compact view to get sample mentions, sentiment, and themes.

Instructions

Return a frozen Cloudflare Workers research snapshot. Omit view or set view=full for the complete fixture; view=compact slices mentions and citations to 8 and clears theme examples; query and filters are ignored because the snapshot is fixed; extra keys besides view are rejected; {} is valid. Use this free fixture when you need a sample payload; for liveness use get_health instead; for list price use get_pricing instead; for live mentions use research_mentions. Never charges, never hits live sources, and does not consume the shared 10-call trial.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`view`	No	Optional snapshot size: full or compact.

Output Schema

TableJSON Schema

Name	Required	Description
`meta`	Yes	Request metadata including billing and freshness
`query`	Yes	Echo of the researched query
`themes`	Yes	Ranked themes extracted from mentions
`voices`	No	Top non-placeholder authors by engagement
`volume`	Yes	Mention counts and trend for the window
`signals`	No	Spike and negative-concentration flags for this window
`summary`	No	Executive summary when include_summary was true
`markdown`	No	Deterministic pasteable brief when include_markdown was true
`mentions`	Yes	Cited mention rows (may be empty — empty windows still succeed)
`citations`	Yes	Sources used to build the brief
`sentiment`	Yes	Aggregate and per-class sentiment
`timeframe`	Yes	Echo of the requested window
`share_of_voice`	No	Present when the query is a vs / multi-brand compare

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.2.2Sep 21, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses that the snapshot is fixed, charges nothing, never hits live sources, and doesn't consume the shared trial. It also explains that query/filters are ignored and extra keys are rejected — useful behavioral details not visible 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.

Conciseness5/5

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

The description is dense but every sentence carries information: purpose, parameter semantics, validation, usage routing, and guarantees. It is front-loaded with the main action and avoids filler.

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?

Given the output schema handles return structure, the description covers the remaining context an agent needs: fixed snapshot behavior, validation rules, valid invocation with '{}', and cost/effect guarantees. Nothing important appears to be missing.

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

Parameters5/5

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

The schema already defines 'view' with an enum, and the description enriches this by explaining the concrete effects of compact vs full ('slices mentions and citations to 8 and clears theme examples'), and notes that omitting view is valid. It also clarifies that other keys are rejected.

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?

The description opens with a specific verb and resource: 'Return a frozen Cloudflare Workers research snapshot.' It names sibling tools for alternative uses (get_health, get_pricing, research_mentions), so an agent can immediately tell this tool apart.

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

Usage Guidelines5/5

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

It gives an explicit usage condition ('Use this free fixture when you need a sample payload') and points to alternatives for liveness, pricing, and live mentions. This is direct, unambiguous routing guidance.

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

Deploy Server