Skip to main content
Glama
Sign In

PostPen

by ai.postpen
OverviewDiscussionsAdmin

List inspiration posts

list_inspiration
Read-only

Lists curated LinkedIn posts from the PostPen Inspiration Hub that performed well, newest first. Use these posts to mirror structure, hooks and format only — never copy their text verbatim; credit is not a license. Each post has post_url and embed_url (LinkedIn's official embed), the author and their profile link, posted_date, media_type, topic_tags and format_tags (filter values), why_it_worked (the curator's note), engagement (reactions, comments and reposts when captured, with captured_at), a short excerpt with contact details hidden, and prompts: PostPen social prompts derived from the post (id, title, prompt). get_inspiration returns one post with its full text. Name the author when you draw on a post.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many posts to return. Defaults to 10; values above 25 return 25.
queryNoWords that must all appear in the post text, author name or why_it_worked.
topicNoOnly posts with this topic tag, e.g. ai, career, founder-story.
formatNoOnly posts with this format tag, e.g. listicle, hook-story, pdf-carousel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only/non-destructive, and the description adds real behavioral detail beyond them: newest-first ordering, the full field set returned, that engagement counts exist only 'when captured' with a captured_at timestamp, and that excerpts are redacted for contact details. This is exactly the context annotations cannot carry.

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?

Front-loads purpose and the get_inspiration contrast in the first two sentences, then enumerates return fields compactly. The attribution/licensing advice is arguably redundant with the copy restriction, making it slightly longer than strictly needed.

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?

There is no output schema, so the description carries the return-value burden and does so fully — field list, engagement caveats, redaction, and the sibling pointer for full text. 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.

Parameters3/5

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

Schema coverage is 100%, so each of the four parameters is already documented in the schema, and the description's mention of topic_tags/format_tags as '(filter values)' adds only a modest cross-reference. It gives no extra syntax or matching semantics for query or limit beyond the schema.

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?

States a specific verb and resource ('Lists curated LinkedIn posts from the PostPen Inspiration Hub') plus ordering ('newest first'), and explicitly contrasts with the sibling get_inspiration which 'returns one post with its full text'. An agent can distinguish the two without opening either schema.

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?

Gives clear use guidance — borrow structure, hooks and format but never copy text, and credit the author — and routes full-text needs to get_inspiration. No explicit exclusions versus other siblings (get_insights, list_posts), so it falls short of a 5.

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

All PostPen toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources