Skip to main content
Glama
velesnitski

yt-mcp

by velesnitski

add_attachment

Attach a local file or inline content to a YouTrack issue. Supports binary uploads via base64 encoding for reports, images, or data files.

Instructions

Attach a file to a YouTrack issue.

Two input modes:

  • file_path: upload an existing file from disk (report.html, chart.png, data.xlsx). filename overrides the displayed name. SECURITY: this mode reads a local file whose bytes are then uploaded to a remote issue, so it is confined to an allowlist of directories and is DISABLED unless the operator sets YOUTRACK_ATTACHMENT_ROOTS. Prefer the content mode below.

  • content + filename: upload generated/inline content with no temp file. Text is UTF-8 encoded; set content_base64=True to upload binary you already hold as base64 (e.g. a screenshot).

For plain-text or markdown reports, prefer add_comment — it renders inline, is searchable, and notifies watchers. Reach for this when the artifact is binary (HTML/Excel/PDF/image) or a downloadable file is genuinely wanted.

Args: issue_id: Issue ID or URL. file_path: Path to a local file to upload (mode A). content: Inline content to upload (mode B; requires filename). filename: Display name. Required for content; optional override for file_path (defaults to the file's basename). content_base64: Treat content as base64-encoded binary. mime_type: Override the auto-detected MIME type. instance: YouTrack instance (optional).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentNo
filenameNo
instanceNo
issue_idYes
file_pathNo
mime_typeNo
content_base64No

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses two modes, security constraints, encoding behavior, filename defaults, and MIME override. However, does not explicitly state that it is a write operation or describe the return value (though output schema exists).

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?

Well-structured with summary, bullet points for modes, sibling comparison, and args list. Every sentence adds value, no redundancy.

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?

Covers all 7 parameters, usage scenarios, security notes, and comparison with sibling. Output schema exists so return value not required. Complete for complexity.

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 description fully compensates by explaining each parameter (issue_id, file_path, content, filename, content_base64, mime_type, instance) with usage details, defaults, and conditional requirements.

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?

Clearly states 'Attach a file to a YouTrack issue', specifies two input modes (file_path and content), and distinguishes from sibling add_comment.

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

Usage Guidelines5/5

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

Explicitly advises when to use add_comment instead (plain-text/markdown) and when to use this tool (binary files). Also warns about security restrictions for file_path mode and recommends preferring content mode.

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/velesnitski/yt-mcp'

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