Akiflow MCP Server

create-task-from-action-item

Convert a meeting recording's action item into an Akiflow task, bridging action items to your task list.

Instructions

Create an Akiflow task from a meeting recording's action item. Bridges meeting action items into your task list.

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": {
      "recording_id": "<recording_id>",
      "action_item_id": "<action_item_id>"
    },
    "name": "create-task-from-action-item"
  }
}

Input Schema

Name	Required	Description	Default
`recording_id`	Yes	Recording UUID
`action_item_id`	Yes	Action item ID within the recording

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1May 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the source (action item) but does not mention side effects, permissions, or whether the operation is idempotent for the same action item.

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 two concise sentences, front-loaded with the core purpose, and contains no redundant 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?

For a simple tool with two parameters and no output schema, the description adequately explains purpose and source. Missing details like return value or validation are acceptable given the rules.

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%, so the baseline is 3. The description does not add additional meaning beyond the schema fields.

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 the verb 'create' and the resource 'Akiflow task from a meeting recording's action item', distinguishing it from sibling tools like 'add-task' which are generic.

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 description implies usage context (meeting recording action items) but does not explicitly state when not to use it or contrast with alternatives like 'add-task'.

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