Skip to main content
Glama
YangLiangwei

PersonalizationMCP

by YangLiangwei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_hidden_posts

Retrieve hidden posts for a user, optionally specifying username and limit to control results.

Instructions

    Get user's hidden posts.
    
    Args:
        username: Username (optional, defaults to current user)
        access_token: Optional access token
        limit: Number of items to return (1-100, default 100)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
usernameNo
access_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 full burden of behavioral disclosure. It only states that this is a getter and describes parameters; it does not disclose authentication expectations, side effects, rate limits, or how 'current user' is resolved. This is thin for a tool that may access private user data.

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 tight and front-loaded with the tool's core purpose, followed by a compact parameter list. Every sentence provides useful information with no filler or repetition.

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 simple retrieval tool with an output schema, the description is mostly adequate. However, it leaves ambiguity about authentication context—how 'current user' is determined and whether hidden posts require an access token—which an agent needs to know to call it reliably.

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%, but the description compensates fully by explaining all three parameters: username's default-to-current-user behavior, access_token's optionality, and limit's range and default. This adds meaning well beyond the bare schema definitions.

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 verb 'Get' plus the resource 'user's hidden posts' clearly states the operation and target. It does not explicitly distinguish itself from sibling tools like get_saved_content or get_user_submitted_posts, but 'hidden posts' is a distinct enough resource that the core purpose is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives some usage context by noting that username defaults to the current user and access_token is optional, but it provides no guidance on when to use this tool versus alternatives. There are no exclusions, prerequisites, or pointers to sibling tools for related functionality.

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