Skip to main content
Glama
YangLiangwei

PersonalizationMCP

by YangLiangwei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_sent_messages

Retrieve user's sent messages from personal platforms. Specify a limit (1-100) to control how many messages are returned. Requires privatemessages scope.

Instructions

    Get user's sent messages (requires privatemessages scope).
    
    Args:
        access_token: Optional access token
        limit: Number of messages to return (1-100, default 100)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
access_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the auth requirement (privatemessages scope) and the read-only nature through the verb 'Get.' It does not mention rate limits or explicit no-side-effect statements, but for a simple retrieval tool this is adequate and adds meaningful context beyond the schema.

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 purpose is front-loaded in the first sentence, followed by a compact Args block that covers both parameters with no filler. Every sentence earns its place.

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 two-parameter read tool with an output schema, the description covers purpose, auth, and parameters sufficiently. The only missing piece is explicit guidance on when to choose this over sibling message tools, which is not essential for correctness.

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?

The schema has 0% description coverage, but the description fully compensates by documenting both parameters: access_token is marked optional, and limit is given a range (1-100) and default (100). This adds meaning far beyond the bare schema fields.

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 opens with 'Get user's sent messages,' a specific verb and resource that clearly distinguishes this tool from siblings like get_inbox_messages and get_unread_messages. It also adds the required privatemessages scope, which is directly relevant to correct invocation.

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 scope requirement ('requires privatemessages scope') gives a necessary prerequisite, and the resource name implies when to use it versus alternative message tools. However, it never explicitly names any alternative or states when not to use this tool, leaving the distinction to inference.

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