Skip to main content
Glama
tetmin

Beeper Texts MCP Server

by tetmin

get_media_attachment

Get media content from Beeper message attachments using their URI. Returns base64 image/audio or file path for videos/documents.

Instructions

Retrieve media attachment content by URI from message attachments.

Args:
    attachment_uri: URI from Message.attachments (e.g., "beeper://attachment/{message_id}/{attachment_index}")
    optimize_for_context: For images, resize to ≤1568px max dimension for cost efficiency (default True)

Returns:
    For images: {"type": "image", "mime_type": "image/jpeg", "base64": "..."}
    For audio: {"type": "audio", "mime_type": "audio/mpeg", "base64": "..."}
    For files/videos: {"type": "file"|"video", "mime_type": "...", "filepath": "/path/to/file"}
    For errors: {"error": "description", "uri": "original_uri"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attachment_uriYes
optimize_for_contextNo
Behavior4/5

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

No annotations; description fully covers behavioral traits: resize behavior for images, return types for different media, and error format. Does not mention auth or permissions, but return type details are thorough.

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?

Well-structured with Args and Returns sections. Slightly lengthy but each sentence provides necessary detail. Could be tightened slightly but remains clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema; description provides exact return formats for all media types and handles errors. No annotations; description covers behavioral and parameter details completely for a 2-param tool.

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

Parameters4/5

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

Schema has 0% description coverage; description adds meaning with URI format example and purpose of optimize_for_context. Fully compensates for missing schema descriptions.

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 retrieves media attachment content by URI from Message.attachments, with a specific URI format. This differentiates it from sibling tools like search_message_contents or get_messages.

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

Usage Guidelines4/5

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

Provides clear context for using attachment_uri from Message.attachments and explains the optimize_for_context parameter. Lacks explicit guidance on when not to use it relative to siblings, but the purpose is distinct enough.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tetmin/mcp-beeper-texts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server