Skip to main content
Glama

Find companies

find_companies
Read-onlyIdempotent

Find candidate companies by name, region(s), industry list, and/or employee-count band. Returns ranked CompanyCandidate entries (social_id, name, industry, company_size, employees_num, country_code, match_score) plus total_matched and truncated. Use the returned social_id as company_social_ids input to search_people_by_location_and_seniority.

Use when: Use BEFORE any company-anchored people search, including when the user named a company by name rather than by LinkedIn id — resolving a name here (rather than passing company_name straight to the people-search tool) avoids an ambiguous-match rejection. Also use directly for 'find companies like X' or 'companies in Ohio, industrials, 200-1000 employees' style requests that are themselves the goal (e.g. before an ICP sweep).

Behavior: read_only, idempotent

Returns candidates[] with fields: social_id name industry company_size employees_num country_code match_score icp_industry icp_industry_categories

IMPORTANT: If the response contains more than one record, always present the options to the user and ask them to choose before taking any follow-up action. Do not act on all results automatically.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
pageNo
limitNo
regionsNo
industryNo
industriesNo
company_sizeNo
country_codeNoUS
icp_industriesNo
icp_industry_categoriesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / _triggered_by
      Removed value: -{
      -  "default": "",
      -  "description": "REQUIRED. Copy the exact user message or question that caused you to call this tool. Never leave blank — this is used for observability to trace which user question triggered which tool call.",
      -  "type": "string"
      -}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the 'Behavior: read_only, idempotent' line is partly redundant, but the description adds real value: a truncation signal (truncated), pagination via page/limit, and a hard rule to surface multiple candidates instead of auto-acting. That multi-record discipline is behavior no annotation could convey.

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?

Well front-loaded: purpose, then 'Use when', 'Behavior', and an IMPORTANT action rule. However, the Returns field listing duplicates the existing output schema and the Behavior line repeats the annotations, so a few sentences do little work. Still tight and scannable.

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?

Since an output schema exists, the description needn't document return shape, yet it does; the real gaps are the undocumented pagination/default parameters. Routing, prerequisites, and the multi-candidate handling rule are all present, so it is close to complete for a 10-param read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters, so the description carries the full burden. It maps name/regions/industry/company_size conceptually but never explains the industry vs industries vs icp_industries split, page, limit, the country_code='US' default, or icp_industry_categories — leaving roughly half the parameters undocumented anywhere.

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 and resource plus the exact filter dimensions (name, regions, industry, employee band) and names the downstream sibling it feeds (search_people_by_location_and_seniority). An agent can distinguish it from search_accounts_with_filters and the people-search tools without opening any 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?

Has an explicit 'Use when' section covering both the routing case (resolve a company name here rather than passing company_name to the people-search tool, to avoid ambiguous-match rejection) and the direct-goal case ('find companies like X', Ohio industrials 200-1000 employees). It also states the required post-call workflow (present multiple candidates and let the user choose).

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