Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Post Get

post_get
Read-onlyIdempotent

Retrieve a social media post by ID to view its text, status, schedule, media targets, publish state, errors, published link, and latest metrics.

Instructions

Get a social media post by id: text, status, schedule, media and its targets (one per channel) with publish state, error, link to the published post and latest metrics.

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>",
      "postId": "<postId>"
    },
    "name": "post_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post id (see post_list).
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.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, and non-destructive, so the burden is lower. The description still adds real value by disclosing the returned payload structure, including per-channel targets with publish state, error, published link, and latest metrics, which substitutes for the absent output 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?

One sentence, front-loaded with verb and resource, with the remainder spent entirely on the returned field list. No filler or redundant restatement of the title.

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 two-parameter read with full schema coverage and rich annotations, the description is nearly complete because it spells out the return shape in lieu of an output schema. The only gap is the absence of explicit guidance on when to call this versus related retrieval tools.

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 description coverage is 100%, and both parameters (postId, organizationId) already document where to obtain their values via post_list and organization_list. The description adds no further meaning about the parameters, so the baseline of 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?

The description pairs the specific verb 'Get' with the resource 'a social media post by id' and enumerates what the record contains: text, status, schedule, media, per-channel targets, publish state, error, published link, and latest metrics. That is clear enough for an agent to know it fetches a single post rather than a list, though it never explicitly distinguishes itself from siblings like post_list or post_metrics.

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?

Usage is only implied: 'by id' signals a single-record fetch, and the schema notes point to post_list and organization_list as sources for the ids. There is no explicit statement of when to prefer this over post_metrics or post_analytics, so the agent must infer the routing.

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

Deploy Server

Other Tools