Mencoro

Get a background job

get_job

Read-onlyIdempotent

The status and, once completed, the result of a background job started by discover_brands, suggest_brand_names, discover_keywords, discover_prompts or start_auto_clustering. Poll it every few seconds until status is "completed" or "failed"; do not start the job again while it is pending or running. A discover_prompts job usually finishes within 15 minutes and fails with error.code timed_out after about 30 minutes. A failed job carries error.code (timed_out, provider_failed, submission_failed or internal_error) and error.message, which says what to do next.

Input Schema

Name	Required	Description	Default
`jobId`	Yes
`organizationId`	Yes

Output Schema

Name	Required	Description
`type`	Yes	What the job produces, and therefore the shape of `result`
`error`	No	Why the job failed, and what to do next. Null unless `status` is `failed`.
`jobId`	Yes
`result`	No	The job output, shaped by `type`. Null while the job is still in flight and for a job that failed: it means the result is not known, never that the job produced nothing.
`status`	Yes	A job in `pending`, `running` or `awaiting_retry` is still in flight; `completed` and `failed` are terminal.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

changedOutput schema / description

Previous value: -"An asynchronous job and, once it has completed, its result"New value: +"An asynchronous job and, once it has completed, its result, or once it has failed, why"

addedOutput schema / properties / error

Added value: +{
+  "description": "Why the job failed, and what to do next. Null unless `status` is `failed`.",
+  "properties": {
+    "code": {
+      "description": "A stable code for the kind of failure: `timed_out`, `provider_failed`, `submission_failed` or `internal_error`.",
+      "enum": [
+        "timed_out",
+        "provider_failed",
+        "submission_failed",
+        "internal_error"
+      ],
+      "type": "string"
+    },
+    "message": {
+      "description": "A fixed, readable explanation of the code. It is the same for every job that failed with that code.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}

AddedSep 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial context beyond them: polling cadence, that discover_prompts typically finishes in 15 minutes and times out around 30, and the failure taxonomy (timed_out, provider_failed, submission_failed, internal_error) with error.message guidance.

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?

Front-loaded with the core purpose, then progressive operational detail. Dense but each sentence contributes (poll behavior, timing, error codes). Slightly long, but no filler sentences.

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 polling tool with an output schema and full safety annotations, the description covers behavior, timing, and error handling well. The only gap is identifying the two required inputs, which the schema does not document either.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden of explaining jobId and organizationId, yet neither parameter is described. It implies jobId originates from the job-starting tools but never states the identifier source explicitly, and organizationId is entirely unexplained.

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 first sentence states a specific verb and resource: the status and result of a background job. It also names the exact sibling tools that create such jobs (discover_brands, suggest_brand_names, discover_keywords, discover_prompts, start_auto_clustering), so an agent can immediately place it relative to the job-starting tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit operational guidance: poll every few seconds until status is completed or failed, and do not restart the job while it is pending or running. It also gives an expected timeline and failure conditions, which is exactly the kind of when-to-use context an agent needs to avoid duplicate work.

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

All Mencoro 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.