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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`title`	Yes
`content`	Yes
`folder_id`	No
`content_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

addedInput schema / properties / content_type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Content Type"
+}

First observedAug 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description is not responsible for basic safety disclosure. It adds useful behavioral detail like 'HTML is stored as source' and optional folder placement, giving the agent more context beyond annotations.

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 efficient: a single opening sentence and a compact Args block that lists each parameter with meaningful detail. No filler or redundant statements.

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?

The description covers all parameters, notes defaults and optionality, and there is an output schema (per context signals) so return values need not be explained. It could mention error conditions or uniqueness constraints, but these are not critical for a basic create operation.

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 explaining each parameter: title, content (with content_type interaction), folder_id (optional, root default), and content_type (default and format). This is rich, actionable semantic detail that the schema alone lacks.

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 clear verb ('create') and resource ('markdown or HTML document in the research library'), which distinguishes it from folder creation and other library operations. The mention of content types further clarifies the exact scope.

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?

No explicit when-to-use or alternatives are mentioned. While the purpose is clear, the description does not guide the agent on when to choose this over create_library_folder or update_library_item, relying on inference from the name and sibling context.

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

All Manawa Terminal tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?