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_competitors, 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationId": "<organizationId>",
      "jobId": "<jobId>"
    },
    "name": "get_job"
  }
}

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.

Changed1 schema field changedNov 13, 2026

changedOutput schema / properties / type / enum

Previous value: -[
-  "geo_prompts",
-  "keywords",
-  "query_clustering",
-  "brand_discovery",
-  "brand_name_suggestion"
-]New value: +[
+  "geo_prompts",
+  "keywords",
+  "query_clustering",
+  "brand_discovery",
+  "brand_name_suggestion",
+  "competitor_discovery"
+]

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?

The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds meaningful context beyond that: polling cadence, typical and timeout durations, failure error codes, and what error.message indicates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and polling instructions, then provides timing and error details that directly help an agent use the tool. Every sentence adds operational value with no filler.

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?

The description covers the job lifecycle, polling behavior, timeouts, and failure handling well, and the output schema can carry return-value details. The remaining gap is that neither required parameter is explained, which is notable for an otherwise detailed definition.

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%, and both organizationId and jobId are required but undocumented in the schema. The description only indirectly implies jobId by referring to a started job, and says nothing about organizationId or where either value comes from.

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 and resource: retrieving the status and completed result of a background job. It also names the producer tools (discover_brands, discover_prompts, etc.), clearly distinguishing this polling tool from the tools that start jobs.

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?

It explicitly says to poll every few seconds until status is completed or failed, and warns not to start the job again while it is pending or running. It adds timing expectations for discover_prompts and explains failure codes, giving clear operational guidance.

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.