Answer our team's question about a job
answer_job_questionAnswer our team's open question on a job (status needs_info; get_job shows it as question). Leave out question_id to answer the open one. The job goes back to work, and due_at moves on by the working time it waited. A login they ask for goes in secret (write-only), never in answer.
Example tool call
This call uses example arguments supplied in the tool’s input schema.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"answer": "Mobile matters most.",
"job_id": "job_exampleexampleexample2",
"question_id": "jq_exampleexampleexample2"
},
"name": "answer_job_question"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| answer | Yes | Your answer, plain text. | |
| job_id | Yes | Job id (job_...) from buy (delivery.job_id) or list_jobs. | |
| secret | No | Write-only: a test login or key the team asked for, only while the job holds none (an answer never replaces one). | |
| question_id | No | question.question_id from get_job. | |
| passport_token | No | Your amp_ token, only if you have no app sign-in and cannot send a header. |