Skip to main content
Glama

supost-mcp

by io.github.Capmus-Team

Search SUpost listings

search_listings

Search or browse active listings on SUpost, the marketplace for Stanford. Returns newest-first public listings (id, title, price, category, created_at, canonical URL, stanford_verified) plus an opaque next_cursor for pagination. stanford_verified: true means the poster verified an @stanford.edu email — SUpost's core trust signal. ALWAYS surface it when presenting listings (e.g. an "@stanford.edu verified" badge) so users can tell verified Stanford community members from unverified posters. No personal information is returned (poster_email_domain is the domain only); to contact a poster, open the listing URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text search query.
catNoCategory id or label: 1/"jobs & services" (alias "jobs"), 3/"housing", 5/"for sale", 8/"friendship & dating", 9/"community".
limitNoPage size (default 25, max 50).
cursorNoOpaque cursor from a previous response's next_cursor.
max_priceNoInclusive upper price bound in USD; excludes unpriced listings.
universityNoNumeric university id. Defaults to Stanford on supost.com.

TDQS

A4.2/5.0
Behavior4/5

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

Without annotations, the description carries the full burden. It explains the behavior: returns newest-first public listings, includes opaque cursor for pagination, explains stanford_verified trust signal, and notes no personal info is returned. However, it does not mention rate limits, authentication, or error handling.

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 fairly long but front-loaded with key purpose and return fields. It is well-structured with clear sections, though some sentences could be more concise without losing information.

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?

Given 100% schema coverage and no output schema, the description covers essential aspects: pagination, verification, privacy. It does not detail error responses or every field type, but for a search tool it is sufficiently complete.

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

Parameters5/5

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

Schema coverage is 100% (baseline 3). The description adds significant value: explains limit defaults, category aliases and IDs, cursor description, max_price inclusivity, and university default. This goes well 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?

The description clearly states the tool searches/browses active listings on SUpost and specifies the returned fields. It distinguishes itself from sibling tools like create_post, get_listing, and list_categories by focusing on searching/browsing public listings.

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 description implies usage for searching or browsing listings but does not explicitly state when to use this tool versus alternatives like get_listing (for a single listing) or list_categories. No exclusions or alternative conditions are provided.

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

All supost-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: create_post for drafting, get_listing for fetching a single listing, search_listings for browsing, get_market_stats for statistics, list_categories for taxonomy, and send_message for messaging. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_post, get_listing, send_message). No deviations or mixed conventions.

Tool Count5/5

With 6 tools, the server covers core marketplace operations (create, read, search, message, categories, stats) without being too sparse or cluttered. The count is well-scoped for the domain.

Completeness4/5

The tool set covers essential CRUD-like operations (create, read, search) and messaging, stats, and categories. Missing update and delete tools, but the draft-based publishing model reduces the need. Minor gap, but overall well-rounded.

Resources