companies_listSearch companies, or pass id to fetch one in full (employees, deals, addresses, custom fields).
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Company id. Returns that one company. | |
| limit | No | Default 50. | |
| offset | No | ||
| search | No | Matches name and website. | |
| deleted | No | List recently deleted companies instead (to restore). |
Changes observed during successful MCP inspections.
Input schema / properties / deletedAdded value: +{
+ "description": "List recently deleted companies instead (to restore).",
+ "type": "boolean"
+}Input schema / properties / idAdded value: +{
+ "description": "Company id. Returns that one company.",
+ "type": "string"
+}Input schema / properties / limit / descriptionPrevious value: -"Max results (default 50)."New value: +"Default 50."Input schema / properties / offset / descriptionRemoved value: -"Pagination offset (default 0)."Input schema / properties / search / descriptionPrevious value: -"Free-text search across company name + website."New value: +"Matches name and website."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds valuable behavioral detail beyond that: the id-mode returns the company 'in full' including employees, deals, addresses, and custom fields, which tells the agent what data volume/composition to expect.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with zero waste, front-loading the primary search use case and then the id variant. Every clause carries information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, and the description compensates by describing what a full fetch contains. Pagination defaults and the exact shape of the list response are left to the schema, which is acceptable, but a note on partial vs. full fields for list mode would round it out.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 80%, so the baseline is 3; however the description adds meaning beyond the schema's terse 'Returns that one company' by enumerating the nested data included in id-mode fetches. The `search` and `deleted` params are left to the schema, which is fine at this coverage level.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource (search companies) and explicitly describes the two modes: filtered listing vs. single-company fetch by id. It doesn't mention the companies_manage sibling for write operations, so differentiation is left to the naming convention rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Clearly says to pass `id` for a full single record and mentions the `deleted` path for restore scenarios, giving concrete usage contexts. It stops short of naming alternatives such as companies_manage for mutations, so no explicit when-not guidance exists.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.