GrackerAI

Query AI-visibility data

query_visibility_data

Read-only

Query your brand's AI-visibility data with a read-only GraphQL query (matching get_visibility_schema). Results are automatically filtered to the brands this connection is authorized for — you cannot reach other brands. Pass parameters via variables.

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": {
      "query": "<query>"
    },
    "name": "query_visibility_data"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	A read-only GraphQL query string matching get_visibility_schema.
`variables`	No	Optional GraphQL variables object referenced by the query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnlyHint and openWorldHint, yet the description adds the most decision-relevant behavior: results are automatically scoped to authorized brands and other brands are unreachable. It omits query cost/row limits and error behavior on malformed queries, which keeps it out of the top band.

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?

Three short sentences, front-loaded with purpose, followed by scoping guarantee and the parameter passing instruction. Nothing is redundant and the sibling reference is placed inline where it is needed.

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 only two parameters and full schema coverage, the definition covers what an agent needs to invoke it. What is missing is any statement about the response shape, which is especially relevant since no output schema exists and the return payload is entirely determined by the caller's query.

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%, so the baseline is 3, and the description goes slightly beyond by telling the agent to pass parameters through `variables` rather than inlining them in the query string. That is a genuine usage instruction, though it does not explain the variables object's shape or typical keys.

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 ("query your brand's AI-visibility data") and pins the mechanism ("read-only GraphQL query matching get_visibility_schema"), which cleanly separates it from the sibling schema tool. An agent knows this is the execution tool and that the sibling is its prerequisite for query shape.

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?

Usage context is clear: read-only GraphQL execution, gated behind the get_visibility_schema companion. There is no explicit when-not-to-use guidance, but for a single execution tool with one sibling the implied workflow is unambiguous.

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

All GrackerAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?