Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

List posts

list_posts
Read-onlyIdempotent

Retrieve an account's social posts 30 at a time, filtered by status, network, or deletion, to review scheduled, published, failed, or removed content. Read-only; media links expire shortly.

Instructions

The account's social posts, 30 per page, with id, status, network, text, scheduled time and media, filtered by status (draft, scheduled, posted, failed...) or network; deleted=true lists removed posts. Media links expire after a few minutes. Reads only.

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_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
statusNo
deletedNo
networkNo
account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so "Reads only" is largely redundant. The description does add real value with the 30-per-page page size and the warning that media links expire after a few minutes – a behavioral trait no annotation conveys.

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 dense but well-ordered sentence: resource, page size, returned fields, filters, then the expiry caveat. Nothing is wasted and the most important scoping information comes first.

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

Completeness3/5

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

For a read-only list tool with no output schema, listing the returned fields and flagging media-link expiry covers the essentials. It is still thin on pagination semantics (how to reach later pages) and on the account_id scoping param, which matter for a multi-account agent.

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 effectively 0% in the metadata, and the description only supplies meaning for status, network and deleted; page and account_id get nothing (account_id's meaning lives only in the schema). This is a partial compensation for a low-coverage schema, so a middling score.

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 the resource (the account's social posts) and the returned fields (id, status, network, text, scheduled time, media), which is far more specific than the title alone. It doesn't name the sibling tools it complements (create_post, delete_post, copy_post_to_network), but the listing purpose is unambiguous.

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?

Explains the two filtering modes (status or network) and the special deleted=true switch for removed posts, which implies when to use it. It stops short of saying when to prefer a sibling (e.g. get_* lookups) or that filters are optional, leaving selection guidance 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