Skip to main content
Glama

create_project_note

Create a note in a specified project with name, description, tags, and parent note settings.

Instructions

指定したプロジェクト内にノートを作成します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesプロジェクトID
nameYesノート名
descriptionNoノートの内容
tagsNoタグID
parentNo親ノートID
addToBottomNo一番下に追加するかどうか

Implementation Reference

  • The handler for the 'create_project_note' tool in the CallToolRequestHandler switch statement. It extracts projectId and note data from args, calls createProjectNote on the API, and returns a success message with the created note.
    case 'create_project_note':
      const { projectId: createProjectNoteId, ...noteData } = args;
      const newProjectNote = await this.repsonaAPI.createProjectNote(createProjectNoteId, noteData);
      return {
        content: [
          {
            type: 'text',
            text: `プロジェクト内にノートが作成されました: ${JSON.stringify(newProjectNote, null, 2)}`,
          },
        ],
      };
  • The input schema definition for 'create_project_note' registered in ListToolsRequestSchema. Defines required properties: projectId (string), name (string), and optional: description, tags, parent, addToBottom.
    {
      name: 'create_project_note',
      description: '指定したプロジェクト内にノートを作成します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
          name: { type: 'string', description: 'ノート名' },
          description: { type: 'string', description: 'ノートの内容' },
          tags: { type: 'array', items: { type: 'number' }, description: 'タグID' },
          parent: { type: 'number', description: '親ノートID' },
          addToBottom: { type: 'boolean', description: '一番下に追加するかどうか' },
        },
        required: ['projectId', 'name'],
      },
    },
  • index.js:561-576 (registration)
    The tool 'create_project_note' is registered as part of the tools list returned by ListToolsRequestSchema handler.
    {
      name: 'create_project_note',
      description: '指定したプロジェクト内にノートを作成します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
          name: { type: 'string', description: 'ノート名' },
          description: { type: 'string', description: 'ノートの内容' },
          tags: { type: 'array', items: { type: 'number' }, description: 'タグID' },
          parent: { type: 'number', description: '親ノートID' },
          addToBottom: { type: 'boolean', description: '一番下に追加するかどうか' },
        },
        required: ['projectId', 'name'],
      },
    },
  • The RepsonaAPI.createProjectNote method that makes the actual API request to POST /project/{projectId}/note to create a note.
    async createProjectNote(projectId, note) {
      return this.makeRequest(`/project/${projectId}/note`, 'POST', note);
    }
Behavior2/5

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

No annotations are provided. The description only states the action without disclosing behavioral traits like permissions, side effects, or return values. For a creation tool, more transparency is needed.

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 a single sentence with no unnecessary words. It is efficient and front-loaded with the primary action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 parameters, no output schema, no annotations), the description is insufficient. It does not explain behavior for optional parameters, defaults, or return value, leaving gaps for an AI agent.

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 description adds no extra meaning. While schema descriptions exist, they are basic (e.g., 'project ID'). The description does not enhance parameter understanding 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 a note within a specified project. It effectively differentiates from sibling tools like create_project_note_comment and create_task.

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?

No guidance on when to use this tool vs alternatives (e.g., update_project_note) or prerequisites (e.g., project existence). The description is too brief to aid decision-making.

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/bellx2/repsona-mcp-server'

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