SpiderLook

get_item

Read-onlyIdempotent

Full stored row, current profile, or snapshot series.

kind is post, ad, page, profile, or snapshots. item_id is required for post/ad/page. Profiles and snapshots omit item_id; snapshots honor window_days.

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>",
      "competitor_id": "<competitor_id>",
      "kind": "<kind>",
      "channel": "<channel>"
    },
    "name": "get_item"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes
`channel`	Yes
`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."
`item_id`	No
`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
`competitor_id`	Yes
`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

B3.1/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 shape-of-result context ('full stored row' vs 'current profile' vs 'snapshot series'), though an output schema exists that partly covers that. It says nothing about failure modes (e.g., a wrong kind/item_id combination) or the meaning of the analytics parameters.

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 most important fact (what you get back) and then the kind-routing rules. Nothing is padded. It is arguably under-specified rather than verbose, but it is efficient.

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?

Nine parameters, four required, and an output schema means the return values need not be explained. Still, for a polymorphic tool where the valid value set of 'kind' and 'channel' determines correctness, the description documents kind but not channel, and gives no hint about what an invalid kind/item_id combination yields.

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?

With only 33% schema description coverage, the description carries meaningful weight and it does deliver: it enumerates the legal kind values (the schema has no enum), states item_id's conditional requirement, and scopes window_days to snapshots. However, 'channel' is required and completely undocumented in both places, and project_id/competitor_id are unexplained, leaving a material gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and its three possible shapes (stored row, current profile, snapshot series) and enumerates the kind values, which does let an agent understand what it fetches. But it opens with a bare noun phrase rather than a verb+resource statement, so the actual action ('retrieve one item') is only inferable from the tool name. No sibling overlap exists, so no differentiation is needed, but the phrasing is cryptically terse.

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?

The second and third sentences give real dispatch guidance: item_id is required for post/ad/page but omitted for profiles and snapshots, and window_days only applies to snapshots. That is useful conditional usage. There is no statement of when to call this versus list_events or query_metrics, though the sibling set offers little genuine ambiguity.

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?