Skip to main content
Glama

Manawa Terminal

Create library item

create_library_item

Create a markdown or HTML document in the research library.

Args:
    title: Document title
    content: Markdown body, or raw HTML when content_type is text/html
    folder_id: Folder UUID (optional — omit for library root)
    content_type: text/markdown (default) or text/html. HTML is stored as source.

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>",
      "content": "<content>"
    },
    "name": "create_library_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
contentYes
folder_idNo
strategy_idNoStrategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.
content_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / strategy_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Strategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.",
      +  "title": "Strategy Id"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / content_type
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Content Type"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world operation, so the safety profile is covered. The description adds useful context that HTML is stored as source and that folder_id may be omitted for the root, but it does not discuss permissions, duplicate handling, or other creation side effects.

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 front-loaded with the core action and then uses a compact Args list for parameter context. Every sentence carries useful information, and there is no unnecessary repetition.

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 create tool with five parameters, an output schema, and annotations covering safety, the description is largely complete: it explains content formats, folder placement, and content defaults. The main gap is that strategy_id is not mentioned in the description, although the schema itself documents it.

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?

With schema description coverage at 20%, the description does substantial work by documenting title, content, folder_id, and content_type, including Markdown-versus-HTML behavior and the folder-root default. It omits strategy_id, though that parameter is already described in the schema, and its stated content_type default differs slightly from the schema default of null.

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 states a specific verb and resource: create a markdown or HTML document in the research library. This clearly distinguishes it from sibling tools such as create_library_folder, update_library_item, and delete_library_item.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains some parameter behavior, such as omitting folder_id for the library root, but gives no explicit guidance on when to use this tool versus update_library_item, create_library_folder, or other library operations. Usage is implied by the name and purpose rather than stated as a decision rule.

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