Skip to main content
Glama

Just List

Add items to a list

add_items

Add items to an existing list the user is on (their own or one shared with them). Use list_my_lists first to find the list id, e.g. for "add milk and eggs to my weekly list". People sharing the list see the items appear.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listId": "<listId>",
      "items": "<items>"
    },
    "name": "add_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesItems to add
listIdYesThe list's id (listId from list_my_lists, create_list or write_list_with_justy)

Output Schema

NameRequiredDescriptionDefault
urlNo
addedNo
titleNo
statusYes
messageYes
notAddedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=false, idempotentHint=false and destructiveHint=false, so safety is covered. The description adds genuine behavioral context annotations do not carry: the add is visible to everyone the list is shared with ("People sharing the list see the items appear") and is restricted to lists the user can access. It does not address what happens when an item already exists, which matters given the non-idempotent hint.

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?

Two tight sentences, front-loaded with the action and scope, then the prerequisite and a single illustrative example. No restatement of the title or filler.

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

Completeness4/5

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

For a two-parameter, low-complexity tool with a full output schema and complete annotation coverage, the description supplies the operational essentials: permission scope, prerequisite lookup, and social side effect. Only the duplicate-item/non-idempotent consequence is left implicit.

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?

Schema coverage is 100% and the listId property already documents that it comes from list_my_lists, create_list or write_list_with_justy. The description repeats that same guidance through the example but adds no new format, batching or duplicate-handling semantics for the items array beyond what the schema states.

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?

States a specific verb and resource ("Add items to an existing list") plus a scope constraint: the list must be one the user is on, either owned or shared with them. The word "existing" implicitly separates it from create_list and draft_list, so the agent can tell what it does without opening the schema.

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?

Gives an explicit prerequisite chain ("Use list_my_lists first to find the list id") and a concrete natural-language example that maps a user utterance onto the tool. It stops short of stating when NOT to use it, e.g. versus write_list_with_justy, so it is clear context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources