Skip to main content
Glama

Just List

Create a list

create_list

Create a new list in the user's Just List account with a title and, optionally, items exactly as given (no Justy). Returns the list's id and link.

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": {
      "title": "<title>"
    },
    "name": "create_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoshopping, todo or general (default general)
itemsNoItems to add, in order
titleYesList title

Output Schema

NameRequiredDescriptionDefault
urlNo
titleNo
listIdNo
statusYes
messageYes
itemCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation profile is partly covered. The description adds genuine value by stating the return payload (id and link) and that items are inserted verbatim, but it says nothing about what happens on repeated calls or whether items are validated/rejected beyond the schema 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?

A single front-loaded sentence carries the action, the optional parameter, the key behavioral caveat, and the return shape with no filler. Nothing in it could be removed without losing information.

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?

All three parameters are schema-documented, an output schema exists for the return value, and the annotations cover safety. The remaining gap is minor: nothing warns that this is non-idempotent, so duplicate calls likely create duplicate lists, which an agent would want to know.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents title, kind, and items with limits and an enum, making 3 the baseline. The description adds real semantics the schema cannot convey: items are stored exactly as supplied with no Justy processing, which changes how an agent should phrase its input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Create a new list") plus the account scope and optional items, so the core action is unambiguous. The parenthetical "(no Justy)" gestures at a contrast with write_list_with_justy without naming it, so the differentiation is implied rather than explicit.

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 "items exactly as given (no Justy)" clause implies this is the path when you have literal content rather than a Justy-mediated draft, which is a useful selection cue. However, no alternative tool is named and there is no explicit when-to-use or when-not-to-use statement, so the agent must infer the routing.

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