Skip to main content
Glama
vialan-art

social-search-mcp

by vialan-art

reddit_search

Read-onlyIdempotent

Search Reddit posts by query, subreddit, sort, and time, returning canonical links in original order; use session cursor for paging without changing query/filters.

Instructions

Search Reddit with original ordering and canonical links. Cursor is valid only within this server session for 15 minutes; keep query and filters unchanged when paging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subNo
sortNorelevance
timeNoall
limitNo
queryYes
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: cursor lifetime is session-scoped to 15 minutes and filters must remain stable across pages, which is not derivable from the schema or annotations.

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?

Two tight sentences with zero filler: purpose first, then the pagination constraint. Every clause carries information the agent needs.

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 6-parameter search tool with no output schema and 0% schema coverage, the definition covers purpose and cursor behavior but omits the semantics of the filtering and sorting parameters that materially change results. Annotations carry the safety profile, so the remaining gap is parameter guidance.

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% across 6 parameters, so the description must carry the burden. It explains cursor semantics well but leaves sub, sort, time, and limit completely undocumented, and the enum members for sort/time are only visible in the raw schema with no explanation of their meaning.

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 a specific verb+resource ('Search Reddit') and adds a distinguishing detail ('original ordering and canonical links') that separates it from the x_* siblings. It never explicitly contrasts itself with siblings like reddit_post, so it falls 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?

Provides real paging guidance ('cursor is valid only within this server session for 15 minutes; keep query and filters unchanged when paging'), which tells the agent how to iterate correctly. However, it says nothing about when to pick this over reddit_post, x_search, or x_post, so usage context is only partially covered.

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