SpiderLook

Add or refresh competitor channel

add_channel

Destructive

Save a channel and request a crawl when the user asks to add or refresh it.

Creates a profile link if absent; reuses matching links. Eligible crawl jobs fetch public channel data and may replace stored analysis. Repeating a call can queue another crawl. Crawls consume available account usage credits and are skipped when scanning is inactive or credits are unavailable; the saved link remains. This tool does not purchase subscriptions or credits. Channels: linkedin, linkedin_person, twitter, instagram, tiktok, youtube, meta_ads, facebook_posts, website, google_ads. facebook_ads and meta alias meta_ads; facebook aliases facebook_posts. Social and ad channels require a matching profile URL; linkedin_person requires linkedin.com/in/..., twitter accepts twitter.com or x.com, and youtube accepts youtube.com or youtu.be. Omit url for website and google_ads; they use the competitor's website.

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": "add_channel"
  }
}

Input Schema

Name	Required	Description
`url`	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."
`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
`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

A4.6/5.0

Behavior5/5

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

Annotations already flag destructive/non-idempotent/open-world, and the description adds substantially beyond them: matching links are reused rather than duplicated, eligible crawls may replace stored analysis, repeated calls queue extra crawls, crawls consume account credits, and skipped crawls still leave the saved link intact. It also bounds scope by stating the tool does not purchase subscriptions or credits.

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?

Front-loaded with purpose and effect, then a dense channel/URL reference block with no filler sentences. It is long, but every line (credit rules, alias mapping, URL formats) carries operational weight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value documentation is unnecessary; the description instead covers side effects, cost, skip conditions, and per-channel input constraints. For a 7-parameter mutation tool with a destructive hint, that is enough for an agent to call it correctly.

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?

With only 43% schema coverage, the description compensates heavily for the undocumented channel and url parameters: it enumerates all valid channel values, documents the facebook_ads/meta and facebook/facebook_posts aliases, and specifies per-channel URL requirements plus the rule to omit url for website and google_ads. It says nothing about project_id/competitor_id, which are conventional identifiers, so it is not fully exhaustive.

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+resource pair ('Save a channel and request a crawl') plus the exact user intent that triggers it ('when the user asks to add or refresh it'). It is clearly distinct from the sibling add_competitor, which manages a different resource, so an agent can route without opening either schema.

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 a clear triggering condition ('when the user asks to add or refresh it') and warns that repeating the call can queue another crawl, which implies a use-vs-reuse decision. It stops short of naming an alternative tool for the 'link already exists' case, but the 'reuses matching links' line covers that behavior.

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?