ic_list_companiesList companies with pagination. Returns company ID, name, website, employee count, and custom attributes.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number | |
| per_page | No | Results per page (default 20) |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | List of companies | |
| error | No | Error code if connection required | |
| pages | No | Pagination metadata | |
| message | No | Error message if connection required |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "data": {
+ "description": "List of companies",
+ "items": {
+ "properties": {
+ "custom_attributes": {
+ "description": "Custom company attributes",
+ "type": "object"
+ },
+ "employee_count": {
+ "description": "Number of employees",
+ "type": "number"
+ },
+ "id": {
+ "description": "Company ID",
+ "type": "string"
+ },
+ "name": {
+ "description": "Company name",
+ "type": "string"
+ },
+ "website": {
+ "description": "Company website URL",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "error": {
+ "description": "Error code if connection required",
+ "type": "string"
+ },
+ "message": {
+ "description": "Error message if connection required",
+ "type": "string"
+ },
+ "pages": {
+ "description": "Pagination metadata",
+ "type": "object"
+ }
+ },
+ "type": "object"
+}Input schema / examplesAdded value: +[
+ {
+ "per_page": 20
+ },
+ {
+ "page": 2,
+ "per_page": 50
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive nature. The description adds return field details but no additional behavioral context beyond pagination, which is already implied by parameters.
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?
Description is a single, front-loaded sentence with no wasted words. It efficiently conveys the core action and return fields.
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?
For a simple listing tool with two parameters and an output schema implied in the description, it covers the essential aspects. Lacks details on ordering or filtering, but these may not be needed given the tool's simplicity.
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 description coverage is 100%, so the parameters are fully documented in the schema. The description does not add new meaning beyond the schema's parameter descriptions.
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?
Description clearly states the tool lists companies with pagination and specifies returned fields. It is specific to listing companies, distinguishing it from sibling tools like ic_search_contacts, though not explicitly contrasting them.
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?
No usage guidance is provided. The description does not mention when to use this tool versus alternatives, nor any prerequisites or exclusions.
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.