Zooq

companies_affiliated_pages

Read-onlyIdempotent

Affiliated / subsidiary / showcase pages of a company. 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
`affiliatedPages`	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": {
+    "affiliatedPages": {
+      "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"
+          },
+          "type": {
+            "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

A4.2/5.0

Behavior4/5

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

The description discloses the 10-Zooq-credit cost and explains that slug resolution is included at no extra credit cost, or that a numeric id skips the lookup. Annotations already cover read-only/idempotent behavior, so the description adds useful non-obvious details beyond them.

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?

Three short sentences front-load the resource and keying mechanism, then add cost information. No wasted words or redundant schema repetition.

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?

For a two-parameter, read-only tool with a full output schema and annotations covering safety hints, the description covers purpose, identifier resolution, and cost. There are no critical gaps for an agent 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, but the description adds meaning by referencing `companies_entity_id` as the source of `id` and by noting slug resolution costs no extra credit. This clarifies how the two optional params relate.

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 opening phrase names the exact resource ('Affiliated / subsidiary / showcase pages of a company'), and the annotation title supplies the verb 'List'. It is clearly scoped to company page relationships, though it does not contrast with sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives clear selection context: use the tool when you need affiliated/subsidiary/showcase pages for a company, and choose `slug` for autolookup or `id` from companies_entity_id to skip lookup. It does not enumerate alternatives or exclusions, but the context is unambiguous.

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?