Skip to main content
Glama
Sign In

Web Crawler MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Crawler Data Query

query_data
Read-only

Query crawler data (Step 4 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id and connected domains

  2. request='available_actions' - Get list of all available crawler actions

  3. request='actions_details' with actions=['xxxx'] - Get detailed body structure for specific action(s)

IMPORTANT: Always call step 3 to see the exact body structure before querying.

Rely on info from steps 1-3 to construct the query body. Follow the schema exactly. Automatically attaches platform='crawler' and handles JSON/text/XML responses.

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": {
      "body": "<body>"
    },
    "name": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
timeout_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context: it automatically attaches platform='crawler' and handles JSON/text/XML responses. It does not explain timeout behavior or error handling, so it is strong but not exhaustive.

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?

Front-loads the workflow role and then uses compact numbered prerequisites with the critical 'Always call step 3' warning. The structure is purposeful and every sentence supports correct invocation.

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?

Output schema exists, so return values need not be described. The description covers the complex part, constructing the query body, and the required preceding workflow. Minor gaps remain around timeout_seconds and error behavior.

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 0%, and the body is a free-form object, so the description compensates by telling the agent to build the body from query_contexts results and to follow the exact structure from actions_details. It meaningfully supplements the schema, though timeout_seconds remains unexplained.

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 ('Query crawler data') and identifies itself as the FINAL workflow step, which clearly distinguishes it from the earlier query_contexts setup calls. An agent can tell what this tool does and where it sits in the sequence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit prerequisites and ordering: complete query_contexts requests for accounts, available_actions, and actions_details first, and 'Always call step 3' before querying. This is exactly the when-to-use guidance an agent needs for a dependent workflow.

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

All Web Crawler MCP by InsightfulPipe toolsInspect
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