Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get post

get_post
Read-onlyIdempotent

Retrieve a single post's status, network, text, scheduled time, media, and any blocking issue by post ID; read-only lookup for review or troubleshooting.

Instructions

One post: status, network, text, scheduled time, media and any problem blocking it. Reads only.

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": {
      "post_id": "<post_id>"
    },
    "name": "get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesThe post's id, from list_posts or get_recording.
account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so "Reads only" is redundant. What does add value is the field inventory of what a post carries and the note that a blocking problem may be reported, since there is no output schema to convey return shape. It still says nothing about behavior for an invalid or not-found post.

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?

A single compact sentence with no filler, front-loaded with the resource and then the payload. The telegraphic fragment style ("One post: ...") is slightly clipped but wastes nothing.

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 simple two-parameter read with no output schema, enumerating the returned fields is the important missing piece and it is supplied here. The only gap is error/no-result behavior and the meaning of "any problem blocking it" (validation failure? account issue?), which an agent might need to interpret the result.

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?

With schema description coverage at roughly 50%, the burden is borderline; both fields do carry schema text, but the description itself contributes no parameter meaning at all. It never clarifies the post_id/account_id relationship or the teammate multi-account caveat beyond what the schema states.

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?

"One post" plus an enumeration of the fields returned (status, network, text, scheduled time, media, blocking problem) makes it unambiguous that this is a single-record fetch, distinct from a listing call. The verb is implied rather than stated, and no sibling (e.g. list_posts) is named to sharpen the contrast, so it stops short of a 5.

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?

The phrase "One post" implies this is the single-record counterpart to a listing tool, but the description never says when to use it versus alternatives or what prerequisites exist. Route information does exist, but only in the schema (post_id "from list_posts or get_recording"), not in the description itself.

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