Skip to main content
Glama
Upload-Post

Upload-Post

Official

List posts awaiting approval

list_pending_approvals
Read-only

List social media posts awaiting team review, filter by status, author, or profile, and count pending approvals. Retrieve a single approval with preview links and publication details.

Instructions

Posts created by team members (Editors and Contributors) that wait for the account owner or an Admin: status pending_approval (an Editor's post, published once approved) or draft (a Contributor's, the reviewer sets the date). By default only open ones, newest first. Each item has approval_id, status, version (needed to approve), profile_username, platforms, post_type, title, caption, platform_content, scheduled_date, expires_at, author_email, author_role, and after a decision decided_by, decision_comment and job_id; closed ones are approved, rejected, withdrawn or expired. With approval_id it returns that one item with its upload fields, preview_url and thumbnail_url (temporary links) and destinations_effective. Editors and Contributors see only their own posts. Page with before = the previous next_before. With count_only: true it lists nothing and answers only counts {status: n} and total for the same filters (status, profile_username, author), e.g. how many posts wait for review. Not generally available yet: until post approvals are switched on for the account, these calls answer 503 post_approvals_disabled (the feature is off, not a temporary failure).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pending_approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1-200. Default 50.
authorNoOnly posts by this team member email.
beforeNo`next_before` of the previous page.
statusNoStatuses to list. Default: the open ones (pending_approval, draft).
count_onlyNoOnly the number of posts per status (`counts`, `total`), no items; limit and before are ignored.
approval_idNo`approval_id` from list_pending_approvals (also returned by an upload that went to approval).
profile_usernameNoOnly this Upload-Post profile.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly annotation it discloses role-scoped visibility (Editors/Contributors see only their own posts), the close-state taxonomy, temporary preview/thumbnail links, that version is needed to approve, and the important 503 post_approvals_disabled feature-gate.

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

Conciseness3/5

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

Waste-free sentences but delivered as one dense paragraph, and the long field enumeration overlaps with what the output schema already provides, making it harder to scan than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool with a rich output schema it covers permissions, defaults, paging, count mode, and the feature-disabled failure mode; nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description adds real semantics: approval_id switches to single-item mode with extra fields, count_only ignores limit/before and returns only counts, and before must be fed the prior next_before.

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?

Names a specific resource (posts by Editors/Contributors in pending_approval or draft) and its scope, and implicitly distinguishes itself from the decision siblings (approve_post, edit_pending_post) by describing the review queue rather than the decision action.

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?

States sensible defaults (only open statuses, newest first), how paging works in place ('before' = previous next_before), and when to prefer count_only for just totals. It does not explicitly point at approve_post/withdraw_pending_post, so routing to the action tool is left implicit.

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