Skip to main content
Glama

add_attachment

Upload binary or downloadable files to a YouTrack issue using local file paths or inline/base64 content, enabling artifact sharing like images, PDFs, and spreadsheets.

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
Install Server

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important operational behavior: file_path mode reads local file bytes and is restricted by an allowlist and environment variable, content mode uses UTF-8 encoding, and content_base64 enables binary uploads. It also explains filename defaulting and MIME auto-detection overrides.

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?

Although lengthy, the description is well structured with clear mode sections and an Args list. Every sentence adds necessary information about usage, security, alternatives, or parameter behavior, so the length is justified.

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?

For a tool with seven parameters, two operational modes, and a security constraint, the description covers everything an agent needs to invoke it correctly. It explains input formats, required parameters, defaults, encoding, and the relationship to add_comment, and an output schema exists for return-value details.

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 carries the full burden, and it succeeds. Every parameter is explained with mode relationships, defaults, required conditions, and behavior—particularly the file_path vs content modes, filename requirements, and content_base64 semantics.

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 a specific verb and resource: 'Attach a file to a YouTrack issue.' It then clarifies two distinct input modes and explicitly differentiates this tool from add_comment, making sibling distinction clear.

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?

The description gives explicit when-to-use guidance: prefer add_comment for plain-text or markdown reports, and use add_attachment for binary artifacts or downloadable files. It names the alternative and the condition that selects between them.

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

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