Skip to main content
Glama
Crawl Readiness MCP Server

Crawl Readiness MCP Server

Read the Answer Analysis

get_monitor_trend
Read-only

Read Answer Analysis data to list brands' AI search share and direction, or detail one brand's trend, competitors, provider breakdown, and example answers.

Instructions

Read the user's Answer Analysis: for the questions a brand's customers ask, how often live AI search (Perplexity, Google AI Overviews) named the brand, which competitors were named, and the change run over run. Call with NO argument to list the user's analyses with each brand's latest share of answers naming it and the direction; pass a brand name or project id to get that brand's full trend, per-provider breakdown, competitor comparison, average position, and short example answers. Reads data existing analyses have already collected — it does not trigger new runs, and it measures rather than promises. Read-only. Requires an API key on a plan that includes Answer Analyses (Monitor, Agency or the audit).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_monitor_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoBrand name or project id to detail. Omit to list all monitored brands.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.4/5.0
Behavior4/5

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

Adds real context beyond the annotations: it reads data already collected, does not trigger new runs, and requires an API key on a qualifying plan (Monitor, Agency, or the audit). Annotations confirm read-only but the description supplies the non-obvious constraint that results are pre-existing, not freshly generated.

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

Conciseness4/5

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

Front-loaded with the resource and its two modes before the access caveats, and every clause carries information an agent needs. Slightly long with a rhetorical tail ('it measures rather than promises') that is marketing rather than operational.

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?

There is no output schema, so the description must describe returns — and it does, enumerating the fields for both list and detail modes. It also covers prerequisites, non-triggering behavior, and read-only scope, leaving nothing essential for correct invocation unstated.

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?

Schema coverage is 100% and the single 'project' param is documented, but the description adds the meaningful consequence of omission (list mode returns each brand's latest share and direction) versus inclusion (full trend, per-provider breakdown, competitor comparison, average position, example answers). That goes beyond the schema's brief note.

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?

States a specific verb and resource: reads the user's Answer Analysis, covering share of answers naming the brand, competitors named, and run-over-run change. It also clearly distinguishes its two operating modes (bare list vs. per-brand detail), so an agent knows exactly what it retrieves.

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?

Explicitly says to call with no argument to list all analyses and to pass a brand name or project id for a single brand's full trend, which is actionable invocation guidance. It lacks an explicit 'when not to use this' or a named alternative among the siblings, though those siblings are unrelated tools.

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