Skip to main content
Glama

add_inventory_item

Add an item to your personal inventory with status (owned, wanted, for-sale), quantity, price, and notes. Use product ID or freeform name.

Instructions

Add an item to the caller's personal inventory. Requires an API key.

One creation tool covers all lifecycle states — set status to match the user's intent: "I bought" → owned, "I want" → wanted, "I'm selling" → for_sale. Either product_id or name must be set. Not idempotent.

Args: api_key: Partle API key (prefix pk_). name: Freeform name for items not yet linked to a Partle product. product_id: Link to a canonical Partle product. status: Lifecycle. Default owned. quantity: How many. Fractional ok. Default 1. notes: Freeform multi-line text — the dumping ground for anything not modeled as a column: extra URLs, comments, where stored, condition narrative, purpose, source, history, log entries. Markdown is fine. Put extra URLs here, not in another field. acquisition_price: What you paid. acquisition_currency: Currency of acquisition_price. purchased_at: ISO date (YYYY-MM-DD). asking_price: For status=for_sale. asking_currency: Currency of asking_price. condition: Free string — typical: new, like_new, good, fair, poor. external_link: Primary click-through URL only (source listing, vendor page, manufacturer page). Exactly one. Additional URLs go in notes as markdown links. external_id: Stable identifier from the source system, used as a dedup key. Per-user unique when set — same external_id can't appear twice for one user. Format is up to you (e.g. aliexpress:1005004714348221, amazon:order/.../line/1, content hash). Leave null for handwritten items. project: Tag for grouping.

Returns: The created inventory row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYes
nameNo
product_idNo
statusNoowned
quantityNo
notesNo
acquisition_priceNo
acquisition_currencyNo
purchased_atNo
asking_priceNo
asking_currencyNo
conditionNo
external_linkNo
external_idNo
projectNo
Behavior5/5

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

Discloses non-idempotency, API key requirement, and details on external_id as a dedup key. Adds value beyond annotations by explaining creation behavior and constraints.

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 bullet points and front-loaded key rules. Although lengthy, each sentence adds value for a complex tool with many parameters.

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 aspects: purpose, parameter details, return value, and constraints. Despite no output schema, the description is thorough and leaves no major gaps.

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?

With 0% schema description coverage, the description fully compensates by providing detailed explanations for each of the 15 parameters, including formats, defaults, and usage notes.

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 'Add an item to the caller's personal inventory' and explains status values for different intents. Distinguishes itself from sibling tools like update_inventory_item and mark_for_sale by being the creation tool.

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 explicit guidance on when to use each status, that product_id or name must be set, and that it's not idempotent. Could improve by explicitly stating not to use for updates, but the sibling list implies that.

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/rubenayla/partle'

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