Skip to main content
Glama

Visibility Genies

Update project context

update_project_context
Destructive

Changes the project's shared memory with a batch of edits, applied in order except competitor additions, which are saved after all the other edits: propose a business fact in a block (proposeFact: one line, with the page it came from as sourceUrl), propose a section or a custom section, withdraw an assistant's open proposal of one, add or remove competitors and key pages, set brand names, append or remove research log entries. Your proposals are used for suggestions at once, labelled as yours, and reach drafts and public text after the customer confirms them on the knowledge base page. Nothing you write changes what the customer confirmed. Do not store figures read from Search Console, Analytics or Google Ads here (no clicks, impressions, positions, sessions, conversions or spend); page topics and business facts are fine. Competitors added here are saved as the Add several box saves them: tracked while Tracking has room under the plan's limit, the rest suggested. Free.

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": {
      "projectId": "<projectId>",
      "updates": "<updates>"
    },
    "name": "update_project_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYesEdits, applied in order except competitor additions, which are saved after all the other edits. Each item is one operation, such as { section, content }, { proposeFact: { block, text, sourceUrl? } } or { addCompetitors: [...] }. Blocks: company, offers, audience, proof_points, original_information, goals, positioning, voice, terms, rules, authors, notes.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
entriesNo
keyPagesYes
sectionsYes
brandNamesYes
competitorsYes
researchLogYes
customSectionsYes
missingSectionsYes
brandCapitalOnlyYes
proposedSectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=false) it discloses the execution order — edits applied in order except competitor additions, which are saved last — plus the proposal lifecycle (labelled as the assistant's, used as suggestions at once, reaching drafts only after customer confirmation, never mutating confirmed facts), and the plan-limit behavior for competitors (tracked while Tracking has room, otherwise suggested) and the cost ('Free').

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the second sentence is a long colon-led run-on enumerating ten operation types, and the important ordering caveat about competitor additions is buried mid-clause. It is information-dense but harder to parse than it needs to be; splitting ordering, proposal semantics, and exclusions into separate lines would read much better.

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 batch mutation tool with an output schema and destructive annotations, this covers ordering, proposal/confirmation semantics, competitor-limit behavior, and a clear data-type exclusion. The only real gap is that it does not distinguish this tool from the similarly purposed update_knowledge_base sibling.

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 meaning: proposeFact is a single line whose sourceUrl is the page it came from, and each batch item is one operation. The remaining operation payloads (brandNames, key pages, research log) are left to the schema, so it improves on the baseline without fully explaining every variant.

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?

The description opens with a concrete verb and resource: 'Changes the project's shared memory with a batch of edits,' then enumerates the operation kinds (proposeFact, custom section, competitors, key pages, brand names, research log). It is far more specific than the title, though it never names a sibling such as update_knowledge_base to disambiguate between the two write paths.

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 an explicit exclusion: do not store Search Console/Analytics/Google Ads metrics here (clicks, impressions, positions, sessions, conversions, spend), while page topics and business facts are fine. It also explains that proposals are used for suggestions immediately but only reach drafts and public text after the customer confirms. What is missing is routing guidance to the sibling update_knowledge_base for confirmed content.

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