campaignstack

Get job applications

campaignstack_get_job_applications

Read-onlyIdempotent

Read job watcher results through one selector. selector.kind='matches' lists postings a watcher found, including found rows nobody acted on yet. selector.kind='applications' lists acted-on applications across the workspace. selector.kind='application' reads one full review payload with letter, screening answers, pending questions, account, resume, and confirmation. Use status filters for found/needs_answer/pending_review/submitted/etc. 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

TableJSON Schema

Name	Required	Description	Default
`selector`	Yes	Choose matches for found postings, applications for acted-on applications, or application for one full review payload.
`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

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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.3/5.0

Behavior4/5

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

Annotations already establish the safe, read-only, idempotent profile, so the description earns credit for adding real behavioral context: the 'application' payload contents and, importantly, the pagination rule ('Results are one page... page through before counting anything'). That pagination guidance is behavior an agent could otherwise get wrong.

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?

The three selector modes are front-loaded and the sentences each carry weight. The closing pagination instructions are slightly dense and repetitive but justified for a paged tool.

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 multi-mode selector tool with an output schema present, the description covers what each mode returns, filtering, and pagination behavior. Coverage is strong, though sibling disambiguation is only implicit.

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% (baseline 3), but the description goes beyond the schema's one-line selector summary by detailing what each kind yields (letter, screening answers, pending questions, etc.) and the meaning of status filters. It adds semantic value over the structured fields.

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?

The description states a specific verb (read) and resource (job watcher results) and immediately decomposes the three selector modes with distinct scopes. An agent can distinguish this from siblings like campaignstack_get_job_watchers (lists watchers) or campaignstack_get_reviews (review queue) without opening a schema.

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 clearly routes between the three selector kinds and explains what each returns, plus when to apply status filters. It stops short of naming alternative sibling tools or explicit exclusions, so it is strong context without full when-not guidance.

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?