Skip to main content
Glama

Perceptlayer

Search data endpoints

search_endpoints
Read-only

Find Perceptlayer endpoints for a website or kind of data. The catalogue has 2454 endpoints across 397 sources, so search before calling. Query with the site and the data you want, e.g. "amazon product reviews", "airbnb listing", "linkedin company", "google maps places", "zillow property". Returns compact matches: endpoint ID (pass it to get_endpoint or call_endpoint), name, HTTP method, credits per call (credits_max when the price depends on the call), tier ("restricted" endpoints need the account's restricted-endpoint terms accepted) and required parameters. Free; no API key needed.

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": {
      "query": "<query>"
    },
    "name": "search_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 10).
queryYesSite and/or data wanted, in a few words, e.g. "tripadvisor hotel reviews".
verticalNoOptional: only return endpoints in this vertical.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely non-obvious behavior: the catalogue size, that the search is free and needs no API key, that "credits_max" appears when pricing is call-dependent, and that "restricted" tier endpoints require accepted restricted-endpoint terms. Those are real operational gates an agent must know about, not restatements of the annotations.

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 purpose and the search-first rationale, then the query pattern, then the return shape, then cost/auth notes. Each sentence carries distinct information — catalogue size justifies the guidance, and the return-field sentence prevents a follow-up clarifying call.

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?

There is no output schema, but the description enumerates the returned fields itself (ID, name, method, credits/credits_max, tier, required parameters), which is what the agent needs to chain into call_endpoint. Combined with the fee and auth statements, nothing material is missing for a 3-parameter search tool.

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 100%, so the baseline is 3, but the description adds meaning for the primary parameter by teaching the composition rule (site + data) and giving five example queries that differ from the schema example. The optional vertical enum is not mentioned in the description, which is the one remaining gap.

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?

Uses a specific verb ("Find") with a named resource ("Perceptlayer endpoints") and a stated scope (website or kind of data). It explicitly positions itself upstream of the siblings by saying the endpoint ID is passed "to get_endpoint or call_endpoint", so the agent can distinguish search from retrieval/invocation without opening another 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 explicit when-to-use guidance: "The catalogue has 2454 endpoints across 397 sources, so search before calling", plus concrete query phrasings ("amazon product reviews", "airbnb listing"). It also routes results onward to get_endpoint/call_endpoint. It stops short of naming when-not-to-use (e.g. when you already have an endpoint ID), though the sibling names make the alternative clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources