Skip to main content
Glama

Refora

Market AI presence

get_market_ai_presence
Read-onlyIdempotent

A market snapshot of the workspace's website from an external index of AI answers: ChatGPT's and Gemini's answers to the brand's buyer questions as users see them in its country (share of answers naming the brand and each competitor, who else they name, which sources they cite), and how often Google's AI Overviews cite the site next to its competitors, month by month, with the questions where a competitor is cited and the site is not.

Use this tool when the user asks how visible they are in AI before their own questions are tracked, or wants the wider market picture next to their own tracking -- phrases like 'does ChatGPT recommend us', 'who does AI recommend instead of us', 'how do we compare in Google's AI answers'.

The snapshot is built once, when the account is created; status 'building' means it is not ready yet. Its numbers are not the workspace's own tracking: read each section's about.

Example question: 'Does ChatGPT recommend Kassaro?'

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "get_market_ai_presence"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesThe workspace's numeric id, as returned by list_workspaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful non-annotation context: the snapshot is built once at account creation and a 'building' status means results are not ready. It does not cover failure modes beyond that state or how stale the monthly data can be.

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 content is front-loaded and every section (contents, when to use, lifecycle caveat, example) earns its place. The opening sentence is an extremely dense run-on that packs six distinct dimensions into one clause chain, and the second sentence's em-dash aside could be split for faster scanning.

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?

With no output schema, the description carries the burden of describing return values, and it does so thoroughly by enumerating the sections and metrics the snapshot reports. The one notable gap is that it never says how the agent should act on 'building' status (retry, inform the user) or whether the snapshot can be regenerated.

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?

There is only one parameter, workspace_id, and the schema already documents it at 100% coverage including provenance ('as returned by list_workspaces'). The description adds no further meaning about the parameter, so the baseline 3 applies.

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 names a specific resource (a market snapshot of the workspace's AI presence) and enumerates exactly what it contains: ChatGPT/Gemini answer share per brand and competitor, who else is named, which sources are cited, and monthly Google AI Overview citation rates. It explicitly distinguishes this from the workspace's own tracking, so an agent can separate it from get_ai_answers or get_visibility_score.

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?

It gives concrete trigger conditions ('does ChatGPT recommend us', 'who does AI recommend instead of us', 'how do we compare in Google's AI answers') plus a worked example question, and states the precondition of use before the user's own questions are tracked. It stops short of naming a specific sibling tool to use instead when the user wants their own tracked data, leaving that routing to inference.

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