Skip to main content
Glama

company get post

company_get_post
Read-onlyIdempotent

Read full Agency post detail and publishing deferrals. Includes firstComment and per-target firstCommentResult (pending|posted|failed|skipped); inspect outcomeUnknown before any manual comment. includeApproval opts in to client approval fields. Verify writes here; asynchronous acceptance does not mean delivery.

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": {
      "workspaceId": "<workspaceId>",
      "postGroupId": "<postGroupId>"
    },
    "name": "company_get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postGroupIdYesExact ID returned by a Company tool; never a personal platformId
workspaceIdYesExact ID returned by a Company tool; never a personal platformId
includeApprovalNoOpt in to client approval fields; omitted by default for compatibility
includeRepostSourceNoOpt in to the saved original-post snapshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / includeRepostSource
      Added value: +{
      +  "description": "Opt in to the saved original-post snapshot",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only establish that this is a safe, idempotent read; the description goes well beyond by disclosing the returned payload categories (firstComment, per-target firstCommentResult with its four states, publishing deferrals, outcomeUnknown) and a non-obvious caveat that async acceptance is not delivery. It also explains that approval fields are opt-in rather than default, which affects interpretation of results.

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?

Four tight sentences, front-loaded with the core purpose, then payload hints, then the caution — no filler. It is compressed to the edge of cryptic ("publishing deferrals" and "outcomeUnknown" are named without elaboration), which slightly hurts scannability but not economy.

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 no output schema, the description rightly carries the return-value burden and covers the operationally important fields plus the async-delivery caveat. It omits the repost-source snapshot entirely, so an agent cannot anticipate that part of the response.

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%, so the schema already documents all four parameters, making 3 the baseline. The description reinforces includeApproval's opt-in semantics but adds nothing about includeRepostSource or the ID format constraints, so it does not exceed the schema.

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?

"Read full Agency post detail and publishing deferrals" gives a specific verb plus resource and signals a detail-level read (contrasting implicitly with the summary tool). It never names the actual siblings (company_get_post_summary, company_get_post_approval, get_post), so an agent must infer the boundary itself.

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

Usage Guidelines4/5

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

The description supplies real usage context: "inspect outcomeUnknown before any manual comment" and "Verify writes here; asynchronous acceptance does not mean delivery" tell the agent when this tool is the right check. It stops short of explicit alternatives or exclusion rules (e.g., use get_post_summary for lightweight listing), which keeps it off a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.