Skip to main content
Glama
YangLiangwei

PersonalizationMCP

by YangLiangwei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_user_submitted_posts

Retrieve submitted posts from a specified user with customizable sort order and limit, enabling personalized, context-aware interactions.

Instructions

    Get user's submitted posts.
    
    Args:
        username: Username (optional, defaults to current user)
        access_token: Optional access token
        limit: Number of posts to return (1-100, default 100)
        sort: Sort order (new, hot, top, default: new)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNonew
limitNo
usernameNo
access_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are present, so the description carries the burden of behavioral disclosure. It only lists parameters and defaults; it does not state read-only behavior, auth requirements, error handling, pagination, rate limits, or edge cases. The verb 'Get' weakly implies a read operation, but little else is disclosed.

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?

The description is compact and front-loaded: one clear intent line followed by a concise args list. Every line adds value, and defaults/ranges are included without redundant prose.

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?

An output schema exists, so return format need not be described. However, the definition omits usage context such as whether OAuth is required for current-user posts, how it relates to sibling Reddit tools, and what happens when no username is provided. It is adequate for invocation but leaves contextual gaps.

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 description coverage is 0%, and the description fully compensates by explaining each parameter: username defaults to the current user, access_token is optional, limit has a 1-100 range with default 100, and sort has an enumerated set with default 'new'. This adds real meaning beyond the raw schema.

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?

The description clearly states the action and resource: getting a user's submitted posts. This is a specific verb+resource pair that is distinguishable from sibling tools like get_user_comments and get_user_overview, though it does not explicitly name them.

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?

Usage is implied: use this tool when you need the posts submitted by a user. However, there is no explicit guidance about when to prefer it over related Reddit tools, no exclusions, and no conditions around when the optional username or access_token should be supplied.

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