Skip to main content
Glama

Edit an entry’s text

update_entry_fields
Destructive

Change an entry’s title, subtitle, name in its own script (native_name, with native_name_lang), description, short name or (on an entry with no Wikidata item) a person’s sourced date of birth (bio), or remove its “from Wikipedia” credit or name the Wikipedia page it came from — a live edit, as the editor saves one: a new revision, audited. Give only what changes; null clears a field. The description is HTML (sanitised on save). A field you change here is no longer managed by the Wikidata sync; to hand one back, so the next sync refreshes it from the item, use set_wikidata_ownership (relinquish_fields). Dry run by default. To ask a reviewer instead, use propose_entry_change.

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

Input Schema

NameRequiredDescriptionDefault
bioNoA person’s date of birth (and optionally birth name and place of birth), each with the address of a source that states it, on an entry with NO Wikidata item; null removes it. The page states it like an item’s facts: for a person only, and only while they are 18 or over. Refused on an entry with a QID, where only the item’s facts are said; linking an item later drops it. On an entry with no kind, saving them makes it a person, in the same revision.
entryYesThe entry: its VHID (11 digits), its short name (as in verifiedhandles.org/<short>), or its Wikidata QID (Q42).
shortNoThe short name in the entry’s URL; null removes it (the VHID URL stays).
titleNo
dry_runNotrue (the default): write nothing — show the change and the exact request it would send. false: make the change.
summaryNoWhy you made this edit, in a few plain words; shown in the entry’s public history. At most 200 characters. Never an internal tracking ID (a backlog or ticket number); a VHID is fine.
subtitleNo
descriptionNo
native_nameNoThe entry’s name in its own script, shown under the title (e.g. 川瀬智子 for Tomoko Kawase); "" or null removes it and its language code. Plain text, at most 200 characters. Setting it takes it from the Wikidata sync, which otherwise fills it from the item’s name in native language (P1559).
idempotency_keyNoOptional: a key you choose (1–255 printable ASCII, e.g. a UUID), sent as the write’s Idempotency-Key. Calling again with the same key and the same change within 24 hours answers the first call’s result (replayed: true) and writes nothing; the same key with another change is refused (422).
base_revision_idNoThe revision you read (get_entry → editing.baseRevisionId). If the entry has changed since, the edit is refused as a conflict. Left out, the current revision is used.
native_name_langNoThe language code of native_name, as Wikidata writes it ("ja", "zh-hant", "ko"); null for none.
credit_wikipedia_pageNoCredit the description “from Wikipedia”: an English Wikipedia article or draft, by title ("Draft:Dominic McLaughlin") or address. The server reads the page (redirects followed) and refuses it unless at least half of the description’s three-word phrases are the page’s lead (credit_text_differs, with the share).
remove_wikipedia_creditNotrue: remove the “from Wikipedia” credit from the description.
credit_let_wikidata_manageNoWith a draft named in credit_wikipedia_page: false keeps the description site-authored. By default a draft’s credit hands the description to the Wikidata sync, which leaves it alone until the draft is an article linked from the entry’s Wikidata item.

Output Schema

NameRequiredDescriptionDefault
noteNoA dry run: what to do next to make the change, in words.
resultNoA real run: the route’s own answer, where the tool adds facts of its own beside it.
confirmNoA dry run of a change that needs it: the exact target to send back as `confirm` with dry_run: false.
dry_runNotrue: a dry run, which wrote nothing. Absent from a real run.
replayedNoA real run with an idempotency_key already used for this change: the first call’s answer, given back; nothing was written now.
would_sendNoA dry run: the exact request the real run would send (`method`, `path`, any `headers` such as an Idempotency-Key, and its `body`, `form` or `query`), or the requests, in order.
may_edit_liveNoA dry run of a live edit: whether this key’s account may edit this entry live.
refused_becauseNoA dry run the real run would be refused for: why, in words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / bio / description
      Previous value: -"A person’s date of birth (and optionally birth name and place of birth), each with the address of a source that states it, on an entry with NO Wikidata item; null removes it. The page states it like an item’s facts: for a person only, and only while they are 18 or over. Refused on an entry with a QID, where only the item’s facts are said; linking an item later drops it."New value: +"A person’s date of birth (and optionally birth name and place of birth), each with the address of a source that states it, on an entry with NO Wikidata item; null removes it. The page states it like an item’s facts: for a person only, and only while they are 18 or over. Refused on an entry with a QID, where only the item’s facts are said; linking an item later drops it. On an entry with no kind, saving them makes it a person, in the same revision."
    • addedInput schema / properties / native_name
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 200,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The entry’s name in its own script, shown under the title (e.g. 川瀬智子 for Tomoko Kawase); \"\" or null removes it and its language code. Plain text, at most 200 characters. Setting it takes it from the Wikidata sync, which otherwise fills it from the item’s name in native language (P1559)."
      +}
    • addedInput schema / properties / native_name_lang
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 35,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The language code of native_name, as Wikidata writes it (\"ja\", \"zh-hant\", \"ko\"); null for none."
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / bio
      Added value: +{
      +  "anyOf": [
      +    {
      +      "properties": {
      +        "birth_date": {
      +          "description": "The date of birth at the precision the source gives: \"2004-10-21\", \"2004-10\" or \"2004\".",
      +          "type": "string"
      +        },
      +        "birth_date_source": {
      +          "description": "The web address (http or https) of a source that states the date of birth.",
      +          "maxLength": 2048,
      +          "type": "string"
      +        },
      +        "birth_name": {
      +          "description": "The birth name, when the source gives one that is not the entry’s name.",
      +          "maxLength": 120,
      +          "type": "string"
      +        },
      +        "birth_name_source": {
      +          "description": "The address of a source that states the birth name (required with it).",
      +          "maxLength": 2048,
      +          "type": "string"
      +        },
      +        "birth_place": {
      +          "description": "The place of birth, as a reader would name it (\"Austin, Texas\").",
      +          "maxLength": 200,
      +          "type": "string"
      +        },
      +        "birth_place_source": {
      +          "description": "The address of a source that states the place of birth (required with it).",
      +          "maxLength": 2048,
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "birth_date",
      +        "birth_date_source"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "A person’s date of birth (and optionally birth name and place of birth), each with the address of a source that states it, on an entry with NO Wikidata item; null removes it. The page states it like an item’s facts: for a person only, and only while they are 18 or over. Refused on an entry with a QID, where only the item’s facts are said; linking an item later drops it."
      +}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that this is a live, audited revision-producing write, that changing a field severs Wikidata sync management for it, that description is HTML sanitised on save, and that credit_wikipedia_page can be refused (credit_text_differs). That is exactly the kind of consequence information destructiveHint alone cannot convey.

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?

Every clause carries information and the editable-field list is front-loaded, but the opening sentence is a long em-dash run-on that an agent must parse carefully. Information-dense rather than padded — trimming would lose real constraints.

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 15-parameter mutation tool this covers the gaps that matter: default dry run, revision conflict via base_revision_id, idempotency replay, ownership handoff, credit validation, and the reviewer alternative. An output schema exists, so return values need not be explained.

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 80%, so the baseline is a 3; the description earns an extra point by adding semantics the schema does not state plainly — "Give only what changes; null clears a field" as the partial-update contract, the native_name/native_name_lang pairing, and the person/18+/no-QID constraint on bio. It does not add much for title, subtitle, description, or summary beyond what the schema already documents.

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 a specific verb and resource, then enumerates exactly which fields are editable (title, subtitle, native_name/native_name_lang, description, short name, bio birth facts, Wikipedia credit). It distinguishes itself from the reviewer path by naming propose_entry_change, so an agent can route correctly 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 Guidelines5/5

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

Explicit when-to-use rules: use propose_entry_change to ask a reviewer instead; use set_wikidata_ownership(relinquish_fields) to hand a field back to the sync; bio only applies to entries with no Wikidata item. Dry run by default is stated, which sets the expected default mode of invocation.

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.