Skip to main content
Glama

Follow Niche

follow_niche

Starts following the niche of a finished scan that has a report: the scan becomes the first measurement and the niche is scanned anew every month, with a digest of what changed sent to the account. Monthly checks do not spend researches; the plan limits how many niches are followed (FREE 1, Starter 2, Pro 10). Following a niche that is already followed returns its project. The niche is followed in the country and the language its scan was measured in (country and language of the project), so every monthly check measures the same audience.

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": {
      "research_id": "<research_id>"
    },
    "name": "follow_niche"
  }
}

Input Schema

NameRequiredDescriptionDefault
research_idYesId of a finished niche scan, or of its report.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-destructive write. The description adds the behavior that matters: a recurring monthly scan, a digest to the account, no research consumption for those checks, per-plan caps, and idempotent return of the existing project. That is exactly the context an agent needs before committing a user to a recurring follow.

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?

The description is front-loaded with the core action, then layers quotas, idempotency, and locale inheritance in descending order of importance. It is dense but every clause carries information; the closing clause about measuring 'the same audience' restates the locale point slightly, a minor redundancy.

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?

For a one-parameter mutation with no output schema, the description covers the preconditions, the recurring side effect, cost implications, quota limits, idempotent behavior, and what is returned ('its project'). Nothing an agent needs to call it safely is missing.

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% for the single required `research_id`, so the baseline is 3. The description adds meaning beyond the schema by explaining that the referenced scan becomes the first measurement and that country and language are inherited from the project, which tells the agent what the id semantically anchors.

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: 'Starts following the niche of a finished scan that has a report.' It also states the ongoing effect (monthly rescans plus a change digest), which no sibling tool (compare_research, find_growth_niches, get_report, etc.) provides, so the agent can identify it 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?

Preconditions are explicit: the scan must be finished and have a report. Idempotency is spelled out ('Following a niche that is already followed returns its project') and the plan quotas (FREE 1, Starter 2, Pro 10) tell the agent when the call will fail. It stops short of naming an alternative tool for the case where the scan is not yet finished.

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.