Zooq

companies_similar

Read-onlyIdempotent

Similar companies / peers (id, name, industry, followers, url). Keyed by the numeric organization id: pass slug and Zooq resolves it for you at no extra credit cost, or pass id from companies_entity_id to skip the lookup. (Costs 10 Zooq credits.)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	Numeric organization id from companies_entity_id; the urn:li:organization: form is accepted. An org_ id (dataset namespace, from companies_info) or a slug placed here is recognized and translated automatically. Provide `id` OR `slug`.
`slug`	No	Company public slug — the part after linkedin.com/company/ — or the full company URL. Resolved to `id` automatically at no extra credit cost. Any company identifier is accepted here and sorted by format (slug, URL, numeric id, org_ id). Provide `id` OR `slug`; `slug` is the simplest.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No	Example value was a number
`SmilarCompanies`	No	Array in the example

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / id / description

Previous value: -"Numeric organization id from /api/v1/companies/entity-id. NOT the org_ id from /companies/universal-name-to-id — that is the dataset namespace and the live endpoints reject it. Provide `id` OR `slug`."New value: +"Numeric organization id from companies_entity_id; the urn:li:organization: form is accepted. An org_ id (dataset namespace, from companies_info) or a slug placed here is recognized and translated automatically. Provide `id` OR `slug`."

changedInput schema / properties / slug / description

Previous value: -"Company public slug — the part after linkedin.com/company/. Resolved to `id` automatically at no extra credit cost. Provide `id` OR `slug`."New value: +"Company public slug — the part after linkedin.com/company/ — or the full company URL. Resolved to `id` automatically at no extra credit cost. Any company identifier is accepted here and sorted by format (slug, URL, numeric id, org_ id). Provide `id` OR `slug`; `slug` is the simplest."

Changed1 schema field changedAug 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structural schema derived from a live example — field names and nesting only, no type constraints: fields may be absent, null, or a different primitive than the example, and new fields may appear. The text content block carries the same JSON.",
+  "properties": {
+    "SmilarCompanies": {
+      "description": "Array in the example",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "followerCount": {
+            "description": "Example value was a number"
+          },
+          "id": {
+            "description": "Example value was a string"
+          },
+          "industry": {
+            "description": "Example value was a string"
+          },
+          "name": {
+            "description": "Example value was a string"
+          },
+          "url": {
+            "description": "Example value was a string"
+          }
+        }
+      }
+    },
+    "count": {
+      "description": "Example value was a number"
+    }
+  },
+  "type": "object"
+}

First observedAug 24, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful operational context: the 10-credit cost, automatic slug/URL resolution at no extra cost, and the ability to skip lookup by providing an id from companies_entity_id. There is no contradiction with annotations.

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?

The description is two sentences with no filler. It front-loads the tool's purpose and output fields, then gives keying and cost details compactly. Every sentence carries useful information.

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?

For a read-only lookup tool with full parameter schema coverage and an output schema, the description covers purpose, return fields, id/slug selection, and cost. It does not discuss pagination or error cases, but those are minor for this tool given the structured annotations and output schema.

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. The description adds value beyond the schema by signaling that slug is the simplest path, that slug resolution carries no extra credit cost, and that passing id from companies_entity_id avoids the lookup. It also reinforces the id-or-slug mutual exclusivity.

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?

The description opens with 'Similar companies / peers' and lists the returned fields (id, name, industry, followers, url), so the resource and output are clear. It lacks an explicit verb and does not name a sibling tool to distinguish itself from, but the purpose is still readily identifiable.

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?

It gives invocation guidance by explaining the keying options ('pass slug... or pass id from companies_entity_id') and mentions the credit cost. However, it does not explicitly state when to prefer companies_similar over nearby alternatives like companies_info or companies_enrich, so tool-selection guidance is mostly implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Zooq tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?