SpiderLook

query_activity

Read-onlyIdempotent

Scraped posts, ads, or pages for one channel, windowed and newest first.

Primary evidence tool. Read these items and form your own answer; do not look up Spiderlook's stored channel-strategy writeup. Instagram feed vs reels is variant=feed|reel|all, not a separate channel. 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>",
      "competitor_id": "<competitor_id>",
      "channel": "<channel>"
    },
    "name": "query_activity"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`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."
`variant`	No		all
`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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: window_days is clamped to 1..90 with a default of 30, and results are returned newest first. It does not address pagination behavior via cursor or result cardinality, keeping it at a 4.

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 lead sentence front-loads purpose, scope, and ordering, and the following lines each carry a distinct operational directive. Slightly verbose phrasing ('Read these items and form your own answer; do not look up Spiderlook's stored channel-strategy writeup') is still doing real steering work rather than padding.

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 an output schema present, the description needn't explain return values, and it covers the notable behavioral facts (newest-first, window clamping, variant meaning). The residual gap is which channel strings are valid and how cursor paging works, which is a modest but real omission for a 10-parameter tool.

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?

Schema coverage is only 30%, so the description must compensate, and it partially does by documenting window_days clamping/defaulting and the valid variant values (feed|reel|all) — notable since variant has no enum in the schema. However, limit, cursor, channel format, and the three required IDs remain undocumented in both places, leaving a clear gap.

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?

The first sentence names the resource (scraped posts, ads, pages), the scope (one channel), and the ordering (windowed, newest first), which is enough to distinguish it from query_metrics and get_item. The verb is only implied ('Scraped posts...'), so it stops short of the explicit verb+resource phrasing an ideal definition would use.

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 explicitly frames itself as the 'Primary evidence tool' with the directive to form your own answer rather than consult the stored channel-strategy writeup, which is a genuine use-condition. It also preempts a likely mistake by clarifying that feed vs reels is a variant value, not a separate channel. It never names a sibling tool as an alternative, so it falls short of a 5.

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?