Skip to main content
Glama

add_inventory_product_attachment

Attach a file to an inventory product using a local path, URL, or base64 data. Specify product ID or exact name, filename, and MIME type.

Instructions

Add a file to an inventory product resolved by product ID or exact name. Provide exactly one of filePath, fileUrl, or data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productYesInventory product ID or exact product name. Pass category when duplicate product names may exist.
categoryNoOptional category ID or exact category name used to disambiguate duplicate product names.
filenameYesName of the file to attach to the inventory product.
contentTypeYesMIME type of the file, such as image/png or application/pdf.
filePathNoLocal file path to upload. Mutually exclusive with fileUrl and data.
fileUrlNoRemote URL to fetch and upload. Mutually exclusive with filePath and data.
dataNoBase64-encoded file data for small files. Mutually exclusive with filePath and fileUrl.
descriptionNoOptional media description. Use null on update to clear it.
pinnedNoWhether the media item should be pinned.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior3/5

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

Annotations already indicate a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that it adds a file and reinforces the one-of file source constraint. It does not disclose additional behavioral traits like overwrite behavior or file size limits.

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 a single sentence that effectively communicates the core purpose and a critical constraint. Every word is necessary, with no fluff or redundancy.

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?

Given the presence of an output schema and high schema coverage, the description covers essentials but misses some context: it does not explicitly list the required fields (product, filename, contentType) or explain how the filename parameter is used. The tool has 9 parameters, and the description could be more comprehensive.

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

Parameters3/5

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

The input schema has 100% description coverage for all 9 parameters, so the schema already documents each parameter. The description adds minimal value by restating the mutual exclusivity of filePath, fileUrl, or data. Baseline is 3, and the description does not significantly augment parameter understanding.

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 verb 'Add' and the resource 'file to an inventory product'. It specifies how the product is resolved (by ID or exact name) and the mutual exclusivity of file sources (filePath, fileUrl, or data). This distinguishes it from generic add_attachment or add_inventory_product_photo.

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 description provides a key usage guideline: 'Provide exactly one of filePath, fileUrl, or data.' However, it does not explicitly differentiate from sibling tools like add_attachment or add_inventory_product_photo, nor does it mention when to use this tool over alternatives.

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/dearlordylord/huly-mcp'

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