Skip to main content
Glama

Visibility Genies

Read competitors

read_competitors
Read-only

Read Tracking, Suggested or Ignored competitors, saved Google and AI measurements, evidence, gaps, setup and stable shared defaults. Optional competitorId opens head-to-head comparison. Uses no credits or provider calls. Missing measurements stay null, never zero.

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>"
    },
    "name": "read_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
marketNo
statusNo
aiRangeNo
projectIdYes
competitorIdNo

Output Schema

NameRequiredDescriptionDefault
metaNo
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: zero credit/provider cost and the rule that missing measurements stay null rather than zero, which prevents misreading absent data as a real value. It does not cover cost/limits on head-to-head mode or the shape of the returned bundle.

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?

Three short sentences, front-loaded with the resource and its contents, then the optional comparison mode, then behavioral caveats. The enumeration "setup and stable shared defaults" is somewhat vague filler, but nothing is redundant.

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

Completeness3/5

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

An output schema exists, so return-value explanation is not required, and the description does signal null-vs-zero semantics. Still, a 6-parameter read with nested market and aiRange objects and a cursor deserves at least a note on filtering and paging behavior, which is absent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, but it only explains competitorId (head-to-head) and hints at status via the Tracking/Suggested/Ignored enumeration. It says nothing about cursor pagination, the market locationCode/languageCode pair, or the aiRange model/promptId/countryCode/date fields, leaving most of the 6 parameters undefined.

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?

Names a concrete verb and resource ("Read ... competitors") and enumerates the payload categories: Tracking, Suggested or Ignored competitors, saved Google and AI measurements, evidence, gaps, setup and shared defaults. It also calls out that competitorId triggers a head-to-head comparison, which distinguishes this read from the competitor-refresh siblings. It never explicitly contrasts itself with find_link_competitors or find_serp_competitors, so it is clear but not fully differentiated.

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?

"Optional competitorId opens head-to-head comparison" gives one concrete usage mode, and "Uses no credits or provider calls" is a decision-relevant fact when choosing between reads. However, there is no explicit when-to-use or when-not guidance and no named alternative for discovering new competitors (e.g. find_serp_competitors), so usage is only implied.

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