Skip to main content
Glama

Create a brand project

create_project

Create a project (a product or client) and optionally link its social accounts and brand brief. Content plans written for this project are grounded in these facts; it does not create or publish content.

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": {
      "name": "<name>"
    },
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
brandNo
websiteNo
channel_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuine value by disclosing the downstream effect (plans are grounded in these facts) and the negative scope (no content creation/publishing), but it omits what happens on duplicate names and whether the brand block is optional at runtime.

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?

Two sentences, front-loaded with the core action and scope, with zero filler. The negative-scope clause earns its place by preventing misuse.

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?

For a mutation tool with a nested brand object, 0% schema coverage and no output schema, the description should explain at least the intent of the brand facts and what gets returned. It covers purpose and downstream effect but leaves the bulk of the input surface undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden. It only loosely maps "social accounts" to channel_ids and "brand brief" to the brand object; the nine nested brand fields (icp, tone, offer, proof, banned_claims, etc.) receive no explanation of meaning or format anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create a project (a product or client)" names a specific verb and resource and even glosses the domain term 'project'. The closing clause "it does not create or publish content" implicitly separates it from create_content_item and create_post_draft, though no sibling is named explicitly.

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?

Usage is implied rather than stated: you create a project so that "content plans written for this project are grounded in these facts." There is no explicit when-not-to-use guidance (e.g. duplicates, existing projects, or pointing to list_projects first) and no prerequisites such as required permissions.

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