Skip to main content
Glama

Propose several changes to one Wikidata item, as one group

propose_wikidata_changes
Idempotent

Propose several changes to one item (one no entry links included: its statements are then read live) as ONE proposal (Console → Wikidata → Review shows it as one card with every change ticked; an administrator may untick some, which are dismissed, and approves the rest, which are made in this order, one edit each; a change that does not go through stops the ones after it). Filed as curated by your account and this key, and only proposed: nothing is written to Wikidata here. Trusted editors and administrators may; each change counts toward a trusted editor’s 200 a day, and there is no limit on the changes in one proposal. qid the item, kind the kind of every change (superseded, duplicate or update), evidence the reason they share (why, and the summary you would like, never naming this site), and changes in order, each exactly as propose_wikidata_correction takes one change but without qid, kind or dry_run: a term (set_label, set_description, set_aliases), add_claim, add_reference, replace_reference, add_qualifier, change_qualifier, remove_qualifier, set_rank or supersede, or alone a move_to_item or copy_to_item (its steps are on two items); a change may give an evidence of its own. To move statements to a NEW item (administrators who may approve Wikidata edits): the first change a create_item, with the new item’s fields as propose_wikidata_item takes them (label, description, aliases, entry, its own statements with their references, an instance of among them, and notability), then a move_to_item of each statement of qid with other_qid "step:1": the item is made with each copy (its qualifiers and references as read) in its one edit, and each statement is removed from qid only once the item is made; an item that is not made removes nothing, and a removal that does not go through stops the ones after it. The dry run shows the item as it would be made (would_create). Never a deprecation or a merge, and never two changes to one term in one language, or one value added twice (duplicate_change). Two changes may be to one statement (two qualifiers on it, a qualifier and a reference), and a change may be to the statement an earlier change adds: give its statement_guid as step:N, N that change’s place in the list. Each change is checked as it would be alone, against the item as the changes before it will leave it, and the proposal is filed only if every one passes: a refusal names its step (from 1), and nothing is filed. Audited. Dry run by default: the site checks every change and shows each step it would file, in order (a preferred rank’s end times and the superseded bundle’s steps in their place). The owner’s Wikidata conventions are checked as for propose_wikidata_correction: a new channel ID statement (P2397) needs its title (P1810), and a YouTube handle’s channel must be on the item or added by an earlier change (refused, with step, message and suggestion), and so are a web archive’s copy as a reference’s url, an add_claim the item states already, and a Bluesky handle changed with no DID; the other slips come back as warnings, each naming its step (a second preferred count of one account in another open proposal included, and an account deprecated as not the subject’s while this proposal leaves follower counts of it current: account_counts_apart). An account and its counts deprecated in one call are one group, with no warning; any of them already open apart is taken into it. A change a person proposed before and is still open is taken into the group only when it writes the same thing (the whole value, its qualifiers and rank, and the same reference, the day retrieved aside): the dry run names it (adopts), and the answer (adopted); one written otherwise (another reference, qualifier or rank) refuses the proposal (409 already_proposed, naming its step and the open row’s id), dry run or not, and nothing is filed: leave that change out, or have the open row dismissed first. A proposal of one change gets the answer that change alone gets from propose_wikidata_correction: beside a person’s open change to something else on its statement it is joined to that one’s group as its next step (joins; the answer’s joined and group_id). A change a person dismissed before (the same kind, action, statement, value seen and new value, and the whole value written: a quantity’s range, a new statement’s qualifiers, and its reference, the day retrieved aside) refuses the proposal (409 dismissed, naming its step, with when it was dismissed), dry run or not, and nothing is filed; refile: true files it all the same. An official website (P856; test.wikidata.org’s P206) a proposal adds or changes, and each of the item’s other official websites with no language of work or name (P407; test.wikidata.org’s P77090), gets a step of its own after the proposal’s, adding the language its page declares (its , else its Content-Language header; en-US is English, Q1860), made as an edit of its own once the statement exists; a page that declares no language, several, or one with no item, or that does not load, gets no step, and nothing is guessed. The dry run and the answer name each (website_languages: the step, the language and what the page declared, or left_out with a message), and a reviewer may untick any. A statement the proposal gives a P407 itself is left as given. Wikidata’s own property constraints (P2302) are checked too, from the properties themselves: refused property_scope (a property Wikidata keeps to qualifiers or references, given as a main value: a Discord invite, P9078, whose suggestion is the server’s P9345 statement with the invite as qualifier) and required_qualifier (a new statement without a qualifier its property requires; where the item states the only value it can take, such as a YouTube handle’s one P2397 channel, it is added in the same step and said, required_qualifier_filled); warned leaves_required_statement (a removal or deprecation that leaves another statement without the statement its property requires: its suggestion is the replacement to add in the same proposal) and second_best_value (a second current value of a single-best-value property with the same separator qualifiers: for an account, the P3831 qualifiers main account Q113050542 and alternate account Q113028955, or the superseded bundle). A constraint whose status is “suggestion” only warns.

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": {
      "qid": "<qid>",
      "kind": "<kind>",
      "changes": "<changes>"
    },
    "name": "propose_wikidata_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
qidYes
kindYes
refileNoFile every change even where a person dismissed the same change before (refused 409 `dismissed` otherwise).
changesYesThe changes, in the order they are to be made.
dry_runNotrue (the default): write nothing — show the change and the exact request it would send. false: make the change.
evidenceNoWhy, shared by every change that gives none of its own.

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. Changed1 schema field changed
    • changedInput schema / properties / changes / items / properties / action / enum
      Previous value: -[
      -  "set_label",
      -  "set_description",
      -  "set_aliases",
      -  "add_claim",
      -  "add_reference",
      -  "replace_reference",
      -  "add_qualifier",
      -  "change_qualifier",
      -  "remove_qualifier",
      -  "set_rank",
      -  "supersede",
      -  "move_to_item",
      -  "copy_to_item"
      -]New value: +[
      +  "create_item",
      +  "set_label",
      +  "set_description",
      +  "set_aliases",
      +  "add_claim",
      +  "add_reference",
      +  "replace_reference",
      +  "add_qualifier",
      +  "change_qualifier",
      +  "remove_qualifier",
      +  "set_rank",
      +  "supersede",
      +  "move_to_item",
      +  "copy_to_item"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / refile
      Added value: +{
      +  "description": "File every change even where a person dismissed the same change before (refused 409 `dismissed` otherwise).",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / changes / items / properties / action / enum
      Previous value: -[
      -  "set_label",
      -  "set_description",
      -  "set_aliases",
      -  "add_claim",
      -  "add_reference",
      -  "replace_reference",
      -  "add_qualifier",
      -  "change_qualifier",
      -  "remove_qualifier",
      -  "set_rank",
      -  "supersede"
      -]New value: +[
      +  "set_label",
      +  "set_description",
      +  "set_aliases",
      +  "add_claim",
      +  "add_reference",
      +  "replace_reference",
      +  "add_qualifier",
      +  "change_qualifier",
      +  "remove_qualifier",
      +  "set_rank",
      +  "supersede",
      +  "move_to_item",
      +  "copy_to_item"
      +]
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations it discloses the full workflow: only proposed here, nothing written to Wikidata, dry run by default, administrator ticking/approval, per-change ordering and failure stopping later steps, rate limits, adoption of open changes, 409 behaviors, warnings, and audit. This is far richer than the supplied annotations and is consistent with readOnlyHint=false and destructiveHint=false.

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

Conciseness2/5

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

The content is relevant, but it is delivered as one enormous run-on paragraph with nested parentheses and semicolons, making it hard to scan or front-load key decisions. The description is far longer than needed and would benefit substantially from headings or a structured list of workflow, errors, and 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?

Given the complexity of a batched, multi-step proposal tool with nested change objects, permissions, ordering, adoption, and constraint checks, the description is remarkably complete. Even though an output schema exists, it still explains return-relevant fields such as `adopts`, `adopted`, `joins`, `group_id`, and `website_languages`, so an agent is unlikely to miss required context.

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

Parameters5/5

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

The description adds extensive meaning beyond the 67%-covered schema: it explains what `qid` identifies, that `kind` applies to every change, that `evidence.why` is shared unless a change supplies its own, that `changes` are ordered and mirror the fields of propose_wikidata_correction, and it documents special mechanisms like `step:N`, create_item with move_to_item, and `refile`. This meaningfully compensates for the schema's free-form `changes` items.

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: 'Propose several changes to one item ... as ONE proposal,' and it explicitly contrasts this with the single-change sibling propose_wikidata_correction. An agent can tell that this tool batches multiple changes to one Wikidata item into one reviewable proposal.

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 substantial when-to-use context: multiple changes grouped into one proposal, one change behaving like propose_wikidata_correction, trusted-editor/administrator permissions, and explicit exclusions such as 'Never a deprecation or a merge.' It does not state a crisp routing rule for choosing this over propose_wikidata_correction in every case, but the boundaries are otherwise clear.

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.