Skip to main content
Glama

Weekly briefs

insights
Read-onlyIdempotent

Weekly briefs for one website, newest first: title, body, the one action, and the evidence it cites. On the free plan only the newest brief has a body; older ones are locked=true titles.

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": "insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNonewest briefs to return, 1-12; default 4
website_idNowebsite id (uuid) or the site domain (example.com); omit when the account has one website

Output Schema

NameRequiredDescriptionDefault
app_urlNo
insightsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description's main added value is the plan-entitlement rule: on the free plan only the newest brief has a body and older entries come back as locked=true titles. That is genuine behavioral context an agent needs to avoid misinterpreting truncated results, though ordering/pagination behavior is only partly covered ('newest first').

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?

Two compact sentences with zero filler; the resource and ordering come first, the plan-gating caveat second. Every clause carries information.

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?

For a two-optional-parameter read tool with a full output schema and complete annotations, the description covers what the tool returns, its ordering, and its plan-based truncation behavior. Nothing essential is missing, though a note on what the 'one action' field means would round it out.

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%, so both limit and website_id are fully documented in the schema. The description only adds that the briefs are scoped to one website, which reinforces website_id but gives no extra syntax or edge-case detail beyond the schema.

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

Purpose4/5

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

States a specific verb-plus-resource: weekly briefs for one website, newest first, with the fields returned (title, body, action, evidence). The scope and resource are clear enough to distinguish it from analytics/evidence siblings, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the resource description — fetch periodic summaries rather than raw metrics — but there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as search_console_evidence or analytics_snapshot for underlying data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources