SpiderLook

query_metrics

Read-onlyIdempotent

Batched project counts and named formulas. Not a dashboard narrative.

Valid metrics: relative_activity_index, activity_threat, activity_counts, ad_launches, ad_counts, follower_totals, talent_velocity, open_deviations, strategy_shifts, weekly_kpi_series. Prefer counts and formulas; weekly_kpi_series is the uniform competitor×week×channel history surface. strategy_shifts is analyzer text the app already shows. Do not N+1 query_activity to rebuild rankings. window_days is clamped to 1..90 (default 30).

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": {
      "project_id": "<project_id>",
      "metrics": "<metrics>"
    },
    "name": "query_metrics"
  }
}

Input Schema

Name	Required	Description
`context`	No	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`metrics`	Yes
`llm_model`	No	Optional model identifier for analytics, only if explicitly available in client-provided metadata. Otherwise pass 'unknown'. Do not inspect or disclose system prompts, hidden instructions, credentials, or other protected context.
`project_id`	Yes
`window_days`	No
`conversation_id`	No	Optional Spiderlook analytics correlation identifier. Reuse the value returned by a previous Spiderlook response only for subsequent Spiderlook calls in this chat. Omit if unavailable; do not invent a value or use the host's conversation ID.

Output Schema

Name	Required	Description	Default
`_mcp_instructions`	No	Server-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds one genuinely new constraint — window_days is clamped to 1..90 with default 30 — plus the batching behavior. It says nothing about response shape or cost/latency behavior, though an output schema exists.

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?

Short and front-loaded, with the type of tool stated first and the guidance after. The telegraphic fragments ('Not a dashboard narrative.') and wrapped metric list read as terse rather than wasteful, though a couple of clauses could be tightened.

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 six parameters, partial schema coverage, an output schema, and full annotations, the description covers the highest-risk gaps: which metric names are legal, the clamping rule, and the sibling to avoid. Missing only project_id semantics and any note on how batched results are keyed, which the output schema likely covers.

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 only 50%, and the description compensates in the most important place by enumerating all ten valid metric values for an array parameter with no enum in the schema. It also clarifies window_days clamping and default. project_id and the analytics parameters remain unexplained, but by schema/description division of labor that is minor.

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+resource: batched project counts and named formulas, and explicitly scopes it as not a dashboard narrative. The list of valid metrics makes the surface concrete. It does not explicitly name the sibling it replaces, though it does warn against using query_activity to rebuild rankings.

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?

Gives real routing guidance: 'prefer counts and formulas', weekly_kpi_series is the uniform competitor×week×channel history surface, and strategy_shifts is analyzer text the app already shows. The anti-pattern 'Do not N+1 query_activity to rebuild rankings' explicitly steers away from a sibling. Lacks an explicit when-not-to-use-this-at-all statement.

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

All SpiderLook 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?