Skip to main content
Glama
Sign In
threadr-mcp

threadr-mcp

by msaeedsakib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_post

Submit text or link posts to a subreddit after authentication, specifying title, content, flair, NSFW, and spoiler options.

Instructions

Create a text or link post in a subreddit (requires user auth)

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": {
      "subreddit": "<subreddit>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
nsfwNo
titleYes
contentYes
is_selfNo
spoilerNo
flair_idNo
subredditYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that user auth is required, which is valuable behavioral context, but omits other important traits for a write tool: whether the post is immediately public, moderation/rate-limit behavior, or what happens on failure. Partial coverage only.

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?

A single, front-loaded sentence that is appropriately sized with zero waste. All information is packed efficiently without redundancy.

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 7-parameter mutation tool with no annotations and no output schema, the description is minimal. It covers the core purpose and auth requirement but leaves most parameter semantics and behavioral implications unaddressed, so it is adequate but with clear gaps.

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

Parameters2/5

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

Schema description coverage is 0% for 7 parameters, so the description must compensate but only mentions 'text or link' and the subreddit implicitly. It does not explain is_self, flair_id, nsfw, spoiler, or the title/content length constraints, leaving most parameters undocumented in both places.

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 (create), resource (post), and scope (in a subreddit), distinguishing it from read siblings like search_posts and mutation siblings like edit_post. An agent can immediately tell this is the write operation for new posts.

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?

Implies usage through the auth requirement but does not state when to use this versus edit_post or reply_to_post, nor any prerequisites like required scopes. The differentiation from sibling mutation tools is left to inference.

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