Skip to main content
Glama
Reddit Ads MCP server

Reddit Ads MCP server

by get-mcp-ads

reddit get post job

reddit_get_post_job
Read-onlyIdempotent

Poll a previously created structured Reddit post using its signed job receipt to check processing status or results; only receipts from confirmed creations in the same process are accepted.

Instructions

Poll a previously created structured post using its signed job receipt. Does not accept arbitrary job IDs from another account.

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": {
      "adAccountId": "<adAccountId>",
      "receipt": "<receipt>"
    },
    "name": "reddit_get_post_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYesReceipt returned by a confirmed reddit_create_post in this server process. Valid for seven days.
adAccountIdYesReddit ad account ID (a2_...) listed in REDDIT_ADS_ACCOUNT_IDS, not the business ID.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds the meaningful constraint that receipts are account-scoped and arbitrary job IDs are rejected, which explains a likely failure mode. It omits the seven-day receipt lifetime, which lives only in the schema.

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?

Two short sentences with no filler; the core action leads and the scoping restriction follows immediately.

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?

With an output schema and full annotations in place, the description only needed to cover the action and the receipt-scoping rule, which it does. The one gap is what the polled state looks like and how often to poll, which an agent must infer.

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 coverage is 100% and both parameters are fully documented there, including the seven-day validity and the a2_ account ID format. The description's 'signed job receipt' phrasing reinforces the receipt parameter but adds no syntax or provenance detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'poll a previously created structured post' via a signed job receipt. It is distinguishable from the many reddit_get_* read siblings by the 'job/receipt' framing, though it never names the closest sibling (reddit_get_post) explicitly.

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

Usage Guidelines3/5

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

'Poll a previously created structured post' implies the prerequisite (a prior reddit_create_post) and the repeated-call pattern, and 'does not accept arbitrary job IDs from another account' gives a negative condition. But no alternative is named and no guidance is given on polling cadence or when to stop.

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