Skip to main content
Glama

Search the catalogue

search_tools
Read-onlyIdempotent

Find Apify Actors (ready-made scrapers and data tools) an agent can call for a kind of web data, e.g. 'LinkedIn company headcount', 'Amazon prices', 'Google Maps leads with email'. Returns the best matches with website, price, output fields, required input, page and scoped MCP URL. Filter by website or category.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoThe data you need, in plain words (website, records, fields).
websiteNoOnly Actors for this website, e.g. 'LinkedIn', 'Zillow'. Also returns that website's bundled MCP URL.
categoryNoOnly this category (keys from list_categories).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that by stating what comes back (website, price, output fields, required input, page, scoped MCP URL) — the scoped MCP URL in particular is non-obvious. It omits ranking/limit behavior, which keeps it from a 5.

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?

Two sentences, no filler: the purpose and examples come first, then the return shape, then the filtering options. Every clause earns its place and nothing is repeated from the schema.

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 no output schema, the description correctly explains the return fields, and it covers the filter parameters. What is missing is anything about result count behavior or what an empty result means, but for a read-only four-parameter search this is close to complete.

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 75% with plain descriptions on query, website and category, so the schema carries most of the load. The description adds only the analogy of plain-word data queries and the website-as-filter idea, which the schema already states; the limit parameter's meaning beyond default 8 / max 25 is not addressed anywhere.

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?

Uses a specific verb-plus-resource ('Find Apify Actors') and clarifies what an Actor is with parenthetical examples, then gives three concrete query examples ('LinkedIn company headcount', 'Amazon prices'). It is clear on its own, but it never names how it differs from catalogue siblings like list_websites or get_tool, so it stops short of full sibling differentiation.

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 description implies use when you need web data and cannot name the tool yet, and 'Filter by website or category' hints at narrowing behavior. However, there is no explicit when-to-use versus list_websites, list_categories, or get_tool guidance — an agent must infer that those enumerate while this one searches.

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