PersonalizationMCP

Overview Schema Source Related Servers Discussions Admin

get_user_overview

Retrieve a combined timeline of a user's posts and comments, with options to filter by username, sort order, and limit. Get a comprehensive overview of user activity.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Default
`sort`	No	new
`limit`	No
`username`	No
`access_token`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 15, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries the burden of explaining behavior. It clarifies that the username defaults to the current user, the access token is optional, and the result is a mixed timeline. It does not disclose authentication expectations, error behavior, or rate limits, but for a read-only 'get' operation the provided context is reasonable.

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: one purpose-defining sentence followed by a lean Args block. Every line adds operational value, and the main purpose is front-loaded.

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?

For a simple read operation with an output schema present, the description covers purpose, default behavior, and all parameter constraints. It could be more complete with explicit sibling routing and auth prerequisite notes, but nothing essential to invoking the tool is missing.

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%, so the description must compensate, and it does. It explains all four parameters: username is optional and defaults to the current user, access_token is optional, limit has a 1-100 range with default 100, and sort lists accepted values (new, hot, top) with default new.

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 states a specific verb ('Get'), a specific resource ('user's posts and comments overview'), and the key distinguishing trait ('mixed timeline'). This clearly separates it from sibling tools like get_user_submitted_posts and get_user_comments, which return only one content type.

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 phrase 'mixed timeline' implicitly signals that this tool is for combined posts and comments, which gives some usage context. However, it never explicitly tells the agent when to prefer this over the single-type sibling tools or when not to use it.

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

Deploy Server