campaignstack

Get companies

campaignstack_get_companies

Read-onlyIdempotent

Read companies by ids or page workspace companies in one bounded V2 envelope. Optional includes cover signals, funding, discovery rows, employees, metric history, reviews, news, and a bounded jobs page with filters. Use nearest specialist tools for deeper company intelligence or refreshes; this read does not fetch new data. Results are one page. When pagination reports more, say so rather than presenting the page as the whole set, and page through before counting anything.

Input Schema

Name	Required	Description
`ids`	No	Specific company IDs to hydrate. Max 25.
`limit`	No
`query`	No	Search by name prefix, domain or LinkedIn company URL across this workspace's companies and the shared company database. Returns up to 10, each marked inWorkspace.
`cursor`	No
`include`	No
`workspaceId`	No	Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.

Output Schema

Name	Required	Description	Default
`items`	Yes
`warnings`	No
`missingIds`	No
`pagination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

addedInput schema / properties / query

Added value: +{
+  "description": "Search by name prefix, domain or LinkedIn company URL across this workspace's companies and the shared company database. Returns up to 10, each marked inWorkspace.",
+  "maxLength": 120,
+  "minLength": 2,
+  "type": "string"
+}

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach."New value: +"Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too."

AddedSep 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower. The description adds genuinely useful behavior: it is a pure read that does not refresh data, results are a single page, and the agent should disclose truncation rather than present a page as the whole set. It omits rate limits or auth requirements.

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?

Four sentences, front-loaded with the two operating modes, then includes, then routing, then pagination caveat. The final pagination sentence is slightly instructional rather than definitional, but every sentence carries information the agent needs.

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?

An output schema exists, so return-shape explanation is unnecessary; the description still covers the key operational caveats (single page, no new data, include catalog) for a nested-schema tool. Missing only explicit mention of the workspaceId defaulting behavior and limits on id hydration, though those live in the schema.

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

Parameters3/5

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

Schema coverage is 50%; the schema already documents ids, query, jobs and workspaceId. The description enumerates the include options (signals, funding, discoveries, employees, metricHistory, reviews, news, jobs with filters), reinforcing the include object, but adds no semantics for limit, cursor, or the workspaceId resolution rules, and no detail on filter syntax.

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 (Read) and resource (companies) plus the two distinct modes of operation: hydration by ids and paging of workspace companies. It also scopes the payload ('one bounded V2 envelope'), which separates it from export/enrich/lookup siblings.

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?

Explicitly says when NOT to use it ('this read does not fetch new data') and points to specialist tools for deeper intelligence or refreshes, plus pagination guidance. The alternative is described generically as 'nearest specialist tools' rather than named (e.g. enrich_companies, refresh_companies), so the routing is clear but not maximally precise.

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

All campaignstack 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?