Skip to main content
Glama

Visibility Genies

Update the knowledge base

update_knowledge_base
Destructive

Proposes facts for the project's business memory and writes page summaries. Every AI feature in Visibility Genies gets the whole confirmed business memory, then the proposals marked as unconfirmed, and the pages that match its task. Free. 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. A field given replaces the assistants' earlier open fact proposals in its block and never changes what the customer confirmed or an assistant's section proposals. To add one fact without replacing others, use proposeFact in update_project_context. Facts are short sentences on one line (500 characters at most, 20 a field), each optionally naming the page it came from. Summaries are at most 1,000 characters. Write only what the site states, and confirm with the user when unsure. Do not store figures read from Search Console, Analytics or Google Ads here (no clicks, impressions, positions, sessions, conversions or spend).

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoFacts to propose by field, each field with its whole list. Fields: offer, audience, location, price, selling_point, tone, note.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
summariesNoPage summaries to set, by the page's exact address as get_knowledge_base lists it. An empty summary clears it.

Output Schema

NameRequiredDescriptionDefault
metaNo
unknownUrlsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses that proposals are used immediately for suggestions but only reach drafts and public text after customer confirmation, and it precisely scopes what a field write overwrites (earlier open fact proposals in that block) versus what it never touches (customer-confirmed facts, assistant section proposals). Limits (500 chars, 20 facts per field, 1,000-char summaries) are also given. The destructiveHint is thus contextualized coherently; only storage/side effects on prior summaries are not fully narrated.

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?

Front-loaded with the core action and the alternative is placed sensibly, but the middle section is a run-on chain of clauses ('Free. Your proposals are used for suggestions at once, labelled as yours, and reach drafts...') and 'Free' interrupts the operational content. Several constraints are packed into dense sentences rather than grouped, which slows scanning.

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?

For a three-parameter mutation with annotations and an output schema, the description covers scope, replacement behavior, confirmation workflow, sourcing rules, field exclusions, and limits. Return values are delegated to the output schema, which is appropriate, so 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?

With 100% schema coverage the baseline is 3, but the description adds real meaning: a field must carry its whole list, each fact may optionally name its source page, summaries are keyed by the exact address as get_knowledge_base lists it, and an empty summary clears the entry. Character and count limits are repeated from the schema but the replacement semantics for fields and summaries are not in 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?

States two specific verbs and their resources up front: proposes facts into the project's business memory and writes page summaries. It also distinguishes itself from the sibling path for adding a single fact (proposeFact in update_project_context), so an agent can route correctly without inspecting either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative for the adjacent case ('To add one fact without replacing others, use proposeFact in update_project_context'), states a hard when-not ('Do not store figures read from Search Console, Analytics or Google Ads here') with the exact metric list, and adds a sourcing rule plus an escalation rule ('confirm with the user when unsure').

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