Skip to main content
Glama

campaignstack

by io.campaignstack
OverviewDiscussionsAdmin

Apply to job

campaignstack_apply_to_job
Destructive

Start an application for exactly one matched posting. CampaignStack reads the posting, drafts a cover letter in the person's voice, then parks it for review or submits later under the watcher's automatic-mode and account-safety gates. Pass applicationId, or postingId only when exactly one live watcher matched that posting. confirmed:true is required after naming the posting and company and getting explicit approval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmedYesRequired after naming the posting and company and getting explicit approval to apply.
postingIdNoOr a posting id when only one live watcher matched it.
workspaceIdNoWorkspace 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.
applicationIdNoThe match/application id from campaignstack_get_job_applications.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
applicationIdNo
creditAttemptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed10 schema fields changed
    • changedInput schema / properties / applicationId / description
      Previous value: -"The match, from campaignstack_list_job_matches"New value: +"The match/application id from campaignstack_get_job_applications."
    • addedInput schema / properties / confirmed
      Added value: +{
+  "description": "Required after naming the posting and company and getting explicit approval to apply.",
+  "type": "boolean"
+}
    • changedInput schema / properties / postingId / description
      Previous value: -"Or the posting a match found"New value: +"Or a posting id when only one live watcher matched it."
    • changedInput schema / required
      Previous value: -[
-  "workspaceId"
-]New value: +[
+  "confirmed"
+]
    • removedOutput schema / properties / applicationId / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / applicationId / type
      Added value: +"string"
    • removedOutput schema / properties / creditAttempt / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "number"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / creditAttempt / type
      Added value: +"number"
    • removedOutput schema / properties / status / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / status / type
      Added value: +"string"
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=false, and openWorld=true, so the safety burden is partly carried. The description still adds real value by explaining that the tool drafts a cover letter in the person's voice and parks it for review before submitting under automatic-mode and account-safety gates, clarifying what 'apply' actually does.

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?

Three sentences, front-loaded with the verb and scope, then the pipeline, then parameter/precondition rules. Dense but every sentence carries information; no filler or marketing fluff.

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 destructive, non-idempotent mutation with an output schema, the description covers scope, approval precondition, parameter selection, and what happens downstream. It omits failure modes and any rate/permission constraints, but the core is complete enough to invoke correctly.

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 description coverage is 100%, so all four parameters are already documented, including the workspaceId defaulting logic and the postingId 'one live watcher' condition. The description largely restates the schema's confirmed/applicationId/postingId guidance rather than adding format or edge-case detail, making 3 the correct baseline.

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 and resource ('start an application for exactly one matched posting') and distinguishes itself from the read-side siblings like campaignstack_get_job_applications by describing the drafting/parking pipeline it kicks off. An agent can tell what this does without opening the 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?

Gives concrete selection rules: pass applicationId, or postingId only when exactly one live watcher matched, and requires explicit human approval before confirmed:true. It does not name the sibling tools to consult first (e.g. get_job_applications), but the preconditions are clear enough to route correctly.

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

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