Skip to main content
Glama
jacklenzotti

pullpush-mcp

by jacklenzotti

search_submissions

Find Reddit posts by filtering subreddit, author, date range, score, or keyword search.

Instructions

Search Reddit submissions (posts). Supports filtering by subreddit, author, date range, score, and keyword search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch query - searches across all submission fields
sizeNoNumber of results to return (default: 25, max: 100)
sortNoSort order (default: desc)
afterNoReturn results after this date. Accepts epoch timestamp or relative date like '30d', '1y'
scoreNoFilter by score. Use >N, <N, or N for exact match
titleNoSearch in submission titles only
authorNoFilter by author username
beforeNoReturn results before this date. Accepts epoch timestamp or relative date like '30d', '1y'
lockedNoFilter locked posts
over_18NoFilter NSFW content (true = only NSFW, false = exclude NSFW)
spoilerNoFilter spoiler posts
is_videoNoFilter video posts
selftextNoSearch in submission body text only
stickiedNoFilter stickied posts
sort_typeNoField to sort by (default: created_utc)
subredditNoFilter by subreddit name (without r/ prefix)
num_commentsNoFilter by number of comments. Use >N, <N, or N for exact match
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions search and filter capabilities, but omits details like pagination, result format, authentication needs, or rate limits. This under-disclosure is a gap.

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 description is a single sentence that front-loads the core purpose. It is efficient with no wasted words, though briefly listing filters could be slightly more structured.

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

Completeness2/5

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

With 17 parameters and no output schema, the description should compensate by explaining return values or pagination behavior. It only lists filters, leaving the agent unaware of result structure. This incompleteness is a notable deficiency.

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%, with each parameter described in the input schema. The description adds no new meaning beyond a high-level list of filter types, so it does not elevate the baseline score.

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?

The description clearly states the tool searches Reddit submissions (posts), using a specific verb and resource. It also lists supported filter categories, distinguishing it from the sibling tool search_comments.

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?

It provides context that the tool supports various filters, implying use cases for finding submissions. However, it does not explicitly state when to use or avoid this tool versus alternatives, though the sibling differentiation is clear from the name.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jacklenzotti/pullpush-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server