Skip to main content
Glama

Visibility Genies

Create a project

create_project

Create a new project in the user's organization. Free: buys no data. Provide a name, and optionally a domain, a default market (locationCode/languageCode; a languageCode requires a locationCode) and the client to group it under (clientId from list_clients, or newClientName). Returns the created {id, name, domain, locationCode, languageCode, url} and its client; pass the returned id as projectId to other Visibility Genies tools. Call list_projects first to avoid creating a duplicate.

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
nameYesName of the project, 1 to 120 characters.
domainNoRoot domain of the site, such as "example.com", as a bare host without scheme or path. Domain, backlink and rank tools use it as their default target.
clientIdNoId of an existing client (see list_clients) to file the project under. Cannot be combined with newClientName.
languageCodeNoLanguage code such as "en" or "fr". Needs locationCode. When omitted, the location decides it.
locationCodeNoLocation code of the default market, for example 2840 for the United States or 2504 for Morocco. The organization default applies when it is left out.
newClientNameNoName of a client to create together with the project and file it under. Use it in place of clientId.
organizationIdNoWhich organization receives the project. Needed when the user is in several: without it the tool lists them, and the user should confirm the choice before you try again.

Output Schema

NameRequiredDescriptionDefault
metaNo
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read, non-destructive, closed-world write, so the bar is lower. The description still adds real behaviour: the call is 'Free: buys no data' (cost transparency) and, unlike a plain create, it lists organizations and defers creation when organizationId is absent and the user belongs to several. Return-value detail is largely covered by the output schema, so it is a modest add rather than a full behavioural picture.

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?

It is front-loaded with the action, then prerequisites, payload, and the duplicate-avoidance reminder, with almost no filler. The telegraphic fragment 'Free: buys no data' is slightly cryptic for the space it saves, and the single dense third sentence packs return shape, id chaining, and pre-check together.

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?

With annotations covering the safety profile, an output schema covering the response shape, and 100% parameter coverage, the description still supplies the non-obvious pieces: cost, multi-organization resolution behaviour, duplicate prevention, and id reuse downstream. Nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-tool meaning the schema does not: clientId is sourced 'from list_clients', newClientName is the substitute, and the returned id becomes projectId elsewhere. The languageCode-requires-locationCode pairing restates the schema rather than extending it, keeping this below a 5.

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 opens with a specific verb and resource, 'Create a new project in the user's organization,' and immediately scopes it against neighbours by naming list_projects (duplicate check) and list_clients (clientId source). An agent can tell this apart from create_action, create_rank_tracker, or update_project_context without opening a schema.

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?

It gives a concrete pre-call order ('Call list_projects first to avoid creating a duplicate') and a post-call instruction ('pass the returned id as projectId to other Visibility Genies tools'), plus a fallback path when organizationId is missing. It never states when to prefer a different creation/update tool, so it stops short of full when/when-not guidance.

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