Skip to main content
Glama

Create Bike Rows

bike_create_rows

Create one or more rows in an outline, with support for nested children, custom positions, and HTML content.

Instructions

Creates one or more rows with optional nested structure.

Args:

  • structure (array, required): Array of rows to create. Each can have:

    • name (string): Text content (may contain HTML if html=true)

    • type (string, optional): Row type (body, heading, task, code, quote, note, unordered, ordered, hr)

    • children (array, optional): Nested child rows

  • parent_id (string, optional): Parent row ID. If not provided, adds to root.

  • position (string, optional): Where to insert - 'first', 'last' (default), 'before', 'after'

  • reference_id (string, optional): Required for 'before'/'after' positioning.

  • html (boolean, optional): If true, name fields may contain HTML formatting: , , , , ,

Returns: Confirmation: "Created N row(s)"

Examples:

  • Single row: bike_create_rows({ structure: [{ name: "New item" }] })

  • With type: bike_create_rows({ structure: [{ name: "Task", type: "task" }] })

  • Nested: bike_create_rows({ structure: [ { name: "Parent", children: [{ name: "Child" }] } ] })

  • At position: bike_create_rows({ structure: [{ name: "First!" }], position: "first" })

  • Before row: bike_create_rows({ structure: [{ name: "Before X" }], position: "before", reference_id: "Kx9" })

  • With HTML: bike_create_rows({ structure: [{ name: "Click <a href="https://example.com">here" }], html: true })

Errors:

  • "Bike is not running" - Open Bike app first

  • "No document is open" - Open a document first

  • "reference_id is required" - When using before/after without reference_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlNoIf true, name fields may contain HTML formatting (strong, em, code, mark, s, a).
positionNoWhere to insert: 'first'/'last' child of parent, or 'before'/'after' reference_id.last
parent_idNoID of the parent row. If not provided, adds to root level.
structureYesArray of rows to create. Each can have name, type, and children.
reference_idNoRequired when position is 'before' or 'after'.
Behavior5/5

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

The description discloses all relevant behaviors: creation with nesting, positioning, HTML support, and prerequisite errors. Annotations are all false, and the description does not contradict them, fully covering the tool's effects and requirements.

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?

The description is well-structured with clear sections (Args, Returns, Errors, Examples), but is somewhat verbose. However, every sentence adds value, and the examples are particularly helpful.

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?

For a tool with 5 parameters and complex nested options, the description is thorough: it covers all parameters, provides examples for common use cases, and lists error conditions. No output schema exists, but the return format is adequately specified.

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?

While the input schema provides 100% description coverage for parameters, the tool description enhances understanding with detailed examples, nested structure explanations, and usage patterns for each parameter, adding value beyond the schema.

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 clearly states it creates one or more rows with nested structure, using a specific verb and resource. It is distinct from sibling tools like update, delete, and group, establishing a unique purpose.

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?

The description provides context such as optional parent_id, positioning options, and error conditions, but does not explicitly guide when to use this tool versus alternatives like bike_update_row. The naming and sibling list make usage clear.

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/hildersantos/bike-mcp-server'

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