Skip to main content
Glama

campaignstack

by io.campaignstack
OverviewDiscussionsAdmin

Answer job question

campaignstack_answer_job_question
Destructive

Send the person's answers for an application stopped at needs_answer. Answers are saved to the watcher's application profile for future matching questions, then CampaignStack continues the application under review, credit, and account daily-limit gates. Use only answers the person gave you; read every answer back first. confirmed:true is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYes
confirmedYesRequired after reading the answers back and getting explicit approval to send them.
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.
applicationIdYes

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 / answers / items / properties / answer / description
      Previous value: -"The person's own answer"New value: +"The person's own answer, verbatim."
    • changedInput schema / properties / answers / items / properties / question / description
      Previous value: -"The question exactly as pendingQuestions lists it"New value: +"The question exactly as pendingQuestions lists it."
    • addedInput schema / properties / confirmed
      Added value: +{
+  "description": "Required after reading the answers back and getting explicit approval to send them.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "workspaceId",
-  "applicationId",
-  "answers"
-]New value: +[
+  "applicationId",
+  "answers",
+  "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, openWorld and non-idempotent. The description goes further, disclosing that answers are persisted to the watcher's profile for future matching questions and that the application resumes under review, credit, and account daily-limit gates — meaningful side-effect context. It still does not detail what data is destroyed or reversibility.

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 tight sentences, front-loaded with the eligible state and followed by the side effects and the confirmation rule. No filler, though the gating clause is rather dense.

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 values need no explanation. Combined with annotations and schema for workspaceId, the description covers persistence, resumption gates, and the confirmation requirement adequately; only applicationId lacks any documentation.

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?

With only 50% schema coverage, the description must compensate. It clarifies that answers must be the person's verbatim input and that confirmed is required after read-back, but applicationId (required, undocumented in both) remains unexplained, leaving a real gap.

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 (send answers) and resource (application stopped at needs_answer), pinpointing the exact precondition. An agent can distinguish it from campaignstack_apply_to_job or campaignstack_get_job_applications 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?

Gives a clear condition ('Use only answers the person gave you; read every answer back first. confirmed:true is required') and the state gating eligibility (needs_answer). It does not name a sibling alternative or exclusion, but the when-to-use 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 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