Skip to main content
Glama

List Social Posts

list_social_posts
Read-onlyIdempotent

[read] Posts of one social account (account_id or account_uuid), newest first. platform = ig|fb|tw|tt|yt|li|th|tg|bsky; status = SCHEDULED|PROCESSING|PUBLISHED|PARTIAL|FAILED (a draft is SCHEDULED with no schedule_datetime); media_type (ig|fb|th|tg only) = image|video|carousel|album|text|story, whichever the platform has.

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": {
      "platform": "<platform>"
    },
    "name": "list_social_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
statusNo
per_pageNo
platformYes
account_idNo
media_typeNo
account_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / media_type
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Media Type"
      +}
  2. First observed

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 and closed-world, so the safety profile is covered. The description adds genuine behavioral detail beyond that: results are ordered newest-first, and a draft is disclosed as SCHEDULED with no schedule_datetime, which prevents an agent from misreading that status. It omits pagination behavior despite page/per_page being available.

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?

The scope statement is front-loaded and the filter vocabulary is packed into a single semicolon-separated sentence with no filler. Dense but well structured; the long enum run is the only readability cost.

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 7-parameter read tool with no output schema, the description covers the filtering dimensions that matter well. The notable gap is pagination and the case where both account_id and account_uuid are omitted, given the description claims results are for 'one social account'.

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 description coverage is 0%, so the description carries the full burden and largely meets it: it enumerates platform values, status values, media_type values with their platform restriction (ig|fb|th|tg only), and explains the account_id vs account_uuid alternative. Only page and per_page are left undocumented, and it never says what happens when neither account identifier is supplied.

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: posts of one social account, returned newest first, with optional narrowing by platform/status/media_type. It is clearly distinguishable from create_social_post, delete_social_post and list_social_accounts, though it never names those siblings 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?

Usage is implied by the filter vocabulary rather than stated: use it to enumerate an account's posts, optionally filtered by status or media type. There is no explicit when-to-use/when-not guidance and no pointer to alternatives such as get_social_top_posts or social_preview_calendar for other views.

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.

Resources