Skip to main content
Glama

web-api-mcp

Company search

search_companies
Read-only

Search for companies and return their profiles, best match first.

Use it to look up a company by name, or to find companies matching a description (an industry, a product, a place, a size): market and competitor mapping, lead lists, funding research. Prefer it over search plus scrape when the answer is a company's facts rather than a web page.

A profile can carry the website and LinkedIn URLs, description, industry, founding year, employee count, headquarters, funding, annual revenue and web traffic; any field may be missing. The figures are often estimates and not necessarily current: check one that matters on the company's own website with scrape.

There are no location or filter parameters: describe the whole set you want in one query.

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_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA company name or a free-text description of the companies wanted. Say what they do, where and how big, in words.
max_resultsNoMaximum number of companies to return. Profiles are long: ask for what you will use. The response may contain fewer.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely new behavioral context: any profile field may be missing, figures are often estimates and possibly stale, and high-stakes numbers should be re-checked with `scrape`. It does not mention cost, latency, or result-set limits beyond what the schema already states, so it stops short of 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?

Four short paragraphs, each with a distinct job: what it returns, when to use, what the data quality is, and the parameter constraint. The routing advice and the no-filter constraint are front-loaded and there is no filler.

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?

With an output schema present, the description need not enumerate return fields, and it correctly focuses on data-quality caveats and tool selection instead. Combined with readOnly/openWorld annotations and full schema coverage, an agent has everything needed 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?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning on top: it explains that filtering must be expressed inside `query` as free text rather than via separate parameters. It reinforces the schema's note that profiles are long and max_results should be sized accordingly, though it gives no query-syntax guidance beyond the examples.

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?

The first sentence gives a specific verb and resource plus the ordering behavior ("return their profiles, best match first"). It also explicitly separates the tool from `search` plus `scrape` when the target is company facts rather than a web page, so an agent can pick it 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 Guidelines5/5

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

It enumerates concrete use cases (name lookup, industry/product/place/size matching, competitor mapping, lead lists, funding research) and names the alternative to avoid (`search` + `scrape`) with the condition that favors this tool. It also states the negative constraint that no location or filter parameters exist, telling the agent to encode the whole set into one `query`.

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.