Verified Handles
Server Details
Look up people, organisations and things, and their official social media accounts and identifiers.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- jameshaworthcs/verifiedhandles-mcp
- GitHub Stars
- 18
- Server Listing
- Verified Handles MCP server
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Most tools target distinct resources, but several near-duplicate families are easy to confuse: propose_entry_change vs propose_entry_changes, update_entry_fields vs update_entry_handles vs update_entries, propose_wikidata_correction vs propose_wikidata_changes, and comment_on_application vs ask_applicant vs comment_on_my_submission. The verbose descriptions help disambiguate, but selection requires close reading rather than being obvious at a glance.
Names are overwhelmingly consistent snake_case verb_noun patterns (get_entry, list_articles, update_entry_fields, propose_wikidata_correction). Minor deviations include the first-person 'my' in list_my_submissions/comment_on_my_submission, the awkward get_reconcile, and singular/plural pairs that look nearly identical.
47 tools is far beyond the 3–15 well-scoped range and above the 25+ threshold for 'too many'. The broad domain explains some breadth, but many tools are singular/batch or propose/live variants that could be consolidated, making the surface heavy for an agent to navigate.
The set covers entries, proposals, review, applications, articles, media uploads and API keys with substantial depth. However, there are notable gaps: no tool to publish, schedule or unpublish an article despite draft/update tools; no direct create/delete entry (only proposals and reports); no media_catalog tool even though several descriptions reference it; and no settings tool despite mentions of settings-driven behavior.
Publisher details
- Operator
- Verified Handles · Publisher source
- Operator website
- https://verifiedhandles.org/ · Publisher source
- Vendor relationship
- Not applicable
- Documentation
- https://verifiedhandles.org/developers/mcp
- Privacy policy
- Not provided
- Trust center
- Not applicable
- Restrictions
- https://verifiedhandles.org/developers/mcp#access
Available Tools
47 toolsadd_entry_noteAdd an internal noteAInspect
Add a staff-only internal note to an entry (plain text; links are kept). Audited. Dry run by default.
Inputs: text (required), entry (required), dry_run. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
approve_applicationApprove an applicationADestructiveInspect
Approve an open application: the entry is created live from its proposal, your assessment (as it stands, with any field given here changed) is recorded with it, and the applicant is emailed. The dry run warns when the assessment falls short of the policy or an entry already links its Wikidata item. Never your own application unless you could create that entry directly. Audited. Dry run by default.
Inputs: application_id (required), dry_run, wikipedia, registered, +4 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
ask_applicantAsk an applicant for moreAInspect
Ask the applicant a question: it goes on the application’s thread, they are emailed it, and the application waits on them (needs_info) until they reply. Only for an application waiting on a reviewer. Audited. Dry run by default.
Inputs: message (required), application_id (required), dry_run. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
assess_applicationAssess an applicationADestructiveInspect
Save your assessment of an open application against the eligibility policy, without deciding it: give only the fields that change; the rest stay as the application has them. The dry run shows the score it comes to. Audited. Dry run by default.
Inputs: application_id (required), dry_run, wikipedia, registered, +4 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
comment_on_applicationComment on an applicationAInspect
Add a message to an application’s thread — the applicant sees it on their application (and is not emailed). To ask them something and wait for the answer, use ask_applicant. Audited. Dry run by default.
Inputs: body (required), application_id (required), dry_run. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
comment_on_my_submissionComment on my own submissionAInspect
Add a message to one of this key’s own account’s submissions (or, for a reviewer, any they may see): the reviewer reads it with the submission, and the submitter sees it on theirs. Answering a question a reviewer asked on your application sends it back to them. Audited. Dry run by default.
Inputs: id (required), text (required), dry_run. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
delete_entry_noteDelete an internal noteADestructiveInspect
Delete an internal note on an entry (its author, or anyone who manages entries). The audit log keeps what it said. Dry run by default.
Inputs: entry (required), note_id (required), dry_run. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
draft_articleDraft an articleAInspect
Start a new article as a draft, as Console → Articles does: nothing is public until a publisher publishes it. The body comes in Markdown (the default) or HTML and is stored as cleaned HTML, through the site’s allowlist. The slug comes from the title when left out. Give what it is about and mentions (entries: their pages list it under “In the news”), the byline, a topic, and a hero image (an uploaded image’s media id) with its alt text. Audited with the key and the tool. Dry run by default: it shows the cleaned HTML exactly as it would be stored, the slug and the address it would have, the links the body makes (each entry’s title), and what the allowlist took out (dropped: each tag, and each attribute as tag@attribute, with how many), and checks what it can without writing.
Inputs: title (required), dek, body, kind, +10 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
edit_entry_noteChange an internal noteADestructiveInspect
Rewrite one of your own internal notes on an entry (only its author may). Audited. Dry run by default.
Inputs: text (required), entry (required), note_id (required), dry_run. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
find_by_handleFind entries by handleARead-onlyInspect
Which public entries list a handle: “is x.com/someone an official account, and whose?”. Give a profile’s address as url (https://x.com/someone), or platform (its catalog id: twitter, instagram, youtube, …) and value (someone or @someone). Answers each entry’s VHID, title and URL, the handle as the entry lists it, and whether that handle is verified; an empty list when no entry lists it. Case is ignored where the platform ignores it. Email addresses are not looked up.
Inputs: url, value, platform. Returns: The public entries that list a handle.
get_articleRead an articleARead-onlyInspect
One article: its fields (title, dek, slug, topic, hero image and alt text, a data story’s chart, status, dates), its byline and the entries it is about and mentions (each with its current title), and its body as stored (body_html, cleaned HTML) and as Markdown (body_markdown, the editor’s own conversion: an entry link reads Name). markdown_round_trips says whether that Markdown, sent back unchanged, stores the same HTML; where it is false, something (a table’s spans, an image’s size) would change, so edit in HTML. These are the words the article shows now: a save waiting for a publisher is pending_revision, seen in the console’s preview.
Inputs: article (required). Returns: article, preview, latest_revision, pending_revision
get_article_historyAn article’s historyARead-onlyInspect
An article’s revisions, newest first (the last 50): each save, publication, schedule, slug change and taking down, with its action, the status it left, who made it, from where (surface) and their summary. current_revision is what readers see; pending_revision, a save waiting for a publisher.
Inputs: article (required). Returns: id, title, status, revisions, +3 more
get_entriesGet many entriesARead-onlyInspect
Up to 50 entries’ public records in one call, by VHID or short name (not a Wikidata QID: get_entry or search_entries finds an entry by its item), each answered as get_entry answers it signed out — the entry, or not_found — in the order given. A name given twice is answered once.
Inputs: entries (required). Returns: Many entries at once: each key’s answer, in request order.
get_entryGet an entryARead-onlyInspect
One entry, by VHID, short name or Wikidata QID: its public record (title, description, handles, image, URL) and, as editing, what the editor would load for this key — the current revision, the editable fields, every handle with who manages it (the Wikidata sync or the site), which fields the sync manages, and whether this key may edit it live. Without an API key, the public record alone.
Inputs: entry (required), include_platforms. Returns: One entry: its public record and, with an API key, what the editor would load f…
get_entry_historyEntry historyARead-onlyInspect
An entry’s public edit history, newest first (next_offset pages on). A merged entry’s key gives its own history.
Inputs: entry (required), limit, offset. Returns: A page of an entry’s public revision history, newest first.
get_reconcileAn entry against its Wikidata item, value by valueARead-onlyInspect
Console → Wikidata, per entry, as JSON: the entry against its Wikidata item, value by value. fields: the title, subtitle, description and image, each with what VH shows, who keeps it on VH (owner: sync, the Wikidata sync; site, a person), what the item says now (the description: the English Wikipedia article it links) and state (same, differs, or unknown when Wikidata did not answer). handles: every handle the entry or the item holds, with on_vh, owner, what the item says of it as the sync last read it (wikidata: listed, deprecated, ended, outranked, gone, or null when the item never listed it; qualifier_only when it is a YouTube channel ID the item states only as its YouTube handle’s qualifier, “The channel ID is only a qualifier on Wikidata”, which the sync still counts as listed) and whether the two agree. propose, on a value that differs, is the change propose_wikidata_changes could carry for it (a statement to add, or a label or description to set; for a lead image that stands for the item’s logo, logo, the console’s “Replace the logo” with that file; for a handle the item deprecated, or one VH’s handle checker last found dead that the item does not count as current, remove_from_vh: take it off VH with update_entry_handles, never push it back onto Wikidata; for one the item states but no longer counts as current otherwise, set_rank preferred or remove_qualifier on that statement, with its GUID and its end time’s hash as the write wiki has them, write_wiki saying whether it answered; never remove_qualifier for one the sync keeps, which it takes off VH instead); it is null, with pending_id, while that change already waits in Review. remove_after: when the sync takes a handle it keeps off VH (the item deprecated, ended or no longer states it), not before; null otherwise. held_back: values a person took off the entry, which the sync does not add back. pending: what waits in Review for the item. sync: when it was last synced, and whether it waits in the priority queue (queue_entry_sync puts it there). Reads the item live through the sync’s rate limit. Read only.
Inputs: entry (required). Returns: vhid, result
link_article_entriesLink entries to an articleADestructiveIdempotentInspect
Set the entries an article is about and those it mentions (their pages list it under “In the news” once it is live), as a save does. By default the entries given are added (one already linked takes the role given) and those in remove taken off; with replace: true the two lists given are the whole of it. Audited with the key and the tool. Dry run by default: it shows the links before and after.
Inputs: article (required), about, remove, dry_run, +3 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
list_applicationsThe applications queueARead-onlyInspect
Applications for a new entry (Console → Applications), 30 a page: each with its proposal, the applicant’s case, the assessment (the reviewer’s saved one, else what the applicant claims) and its score against the eligibility policy, the entry already on its Wikidata item, and whether this account may approve it. tab: "open" (to review, oldest first), "needs_info" (awaiting the applicant), "approved", "rejected", "spam", "retracted" or "all"; or "proposals", the quick proposals — new entries proposed with no eligibility case (propose_new_entry, the console form), waiting ones oldest first, or with decided: true the decided ones — each with its proposal, the entry already on its item (duplicate) and whether this account may approve it; decide one with review_submission. With application_id, that one application and its comment thread.
Inputs: tab, page, decided, application_id. Returns: id, qid, tab, note, +27 more
list_articlesArticlesARead-onlyInspect
The site’s News articles and guides as Console → Articles has them, every one but a deleted one, newest change first: each with its id, kind, slug, title, status (draft, scheduled, published, unpublished), path, topic, and when it was scheduled, published, last updated for readers (modified_at) and changed. Filter by kind, status, topic or author (an entry: the articles whose byline names it).
Inputs: kind, topic, author, status. Returns: count, articles
list_entry_notesInternal notesARead-onlyInspect
The staff-only internal notes on an entry, oldest first, with what this key may do to each.
Inputs: entry (required). Returns: vhid, notes
list_my_submissionsMy own submissionsARead-onlyInspect
This key’s own account’s submissions — proposed changes, new-entry proposals, claims, reports and applications — newest first, 25 a page: each with its status, its entry, when it was sent and decided, and the reviewer’s notes. status: open keeps the ones still waiting. With id, one submission (yours, or any a reviewer may see) with what it asks and its comment thread.
Inputs: id, page, status. Returns: id, qid, kind, mine, +12 more
list_review_queueThe review queueARead-onlyInspect
Submissions waiting for a reviewer (or, with status, decided ones), oldest first, up to 100: proposed changes (correction), claims and reports, each with its entry and what it asks (a claim says entity_claimed_by_other when another account already holds its entry). New-entry proposals (new_entity) are not listed here: they wait beside the applications, in list_applications with tab "proposals", and are still decided with review_submission. Narrow to one entry or one kind. Decide one with review_submission.
Inputs: kind, entry, status. Returns: count, status, of_first, submissions
mark_application_spamMark an application as spamADestructiveInspect
Mark an open application as spam: it is declined, and the applicant is not told. Cannot be undone. Audited. Dry run by default; the real run needs confirm set to the application’s id.
Inputs: application_id (required), confirm, dry_run. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
propose_entry_changePropose a change to an entryAIdempotentInspect
Propose a change for a reviewer to decide — for any entry you may propose to, including ones you could edit live; nothing changes until a person approves it. Give only what changes; null clears a field. native_name (with native_name_lang) proposes the name in its own script shown under the title. On an entry with no Wikidata item, bio proposes a person’s date of birth (and birth name and place of birth), each with its source. qid proposes linking the entry to a Wikidata item, or a different one (null: unlink it), with adopt naming the fields the item may manage (left out: the server’s default on a first link, unchanged on a re-point); only a reviewer with Manage entries may approve that. note tells the reviewer why. While your own proposal on the entry is still waiting, this change is added to it rather than filed beside it: the answer names that proposal, with folded: true. Audited. Dry run by default: it names the entries already on the item.
Inputs: entry (required), bio, qid, note, +26 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
propose_entry_changesPropose changes to many entriesAIdempotentInspect
Proposals for up to 25 entries in one request, each as propose_entry_change files one (the text fields, handles added and removed) for a reviewer to decide; nothing changes until a person approves each. Audited, with one batch id. Proposing the same change again while it waits answers the same proposal, and a change to an entry where your own proposal is still waiting is added to that one (its result says folded: true). By default each proposal stands alone; with atomic: true, any refused one means none is filed. Dry run by default: it reads each entry and lists what would be proposed.
Inputs: edits (required), atomic, dry_run, idempotency_key. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
propose_entry_revertPropose putting an entry back to an earlier revisionAInspect
Propose, for a reviewer to decide, putting an entry back as it was at one of its revisions (get_entry_history: a ref_id like "r123"; imported legacy revisions cannot be put back). The proposal holds only what differs from now — title, subtitle, description, short name, handles and their order, lead image, gallery — as propose_entry_change would send it; who manages each value (Wikidata or the site) is left as it is. An image withdrawn since is left out, and the answer names it. Refused (nothing_to_change) when the entry already matches that revision. note tells the reviewer why. Audited. Dry run by default.
Inputs: entry (required), revision (required), note, dry_run, +1 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
propose_from_wikidataPropose what a Wikidata item saysAInspect
Propose, for a reviewer to decide, what a Wikidata item says for an entry: its identifier handles, and when asked its label (as the title), its description (as the subtitle) and its image. qid defaults to the item the entry is linked to. For that item, unless the entry is protected or claimed, it proposes handing the values to the Wikidata sync instead of copying them (the sync then writes and keeps them up to date), and says so. For another item it copies the values, which become the site’s own: the sync will not keep them up to date. Handles the entry already has (by each platform’s own rule for letter case) are left out. The entry’s description comes from Wikipedia, not from the item, so it is only ever handed to the sync. Warns when the item is another entry’s. note tells the reviewer why. Audited. Dry run by default: it shows what the item has, what the entry has, and the proposal.
Inputs: entry (required), qid, note, take, +2 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
propose_new_entryPropose a new entryAIdempotentInspect
Propose a new entry for a reviewer to decide: it waits in Console → Applications under Quick proposals (list_applications with tab "proposals") and becomes live when approved. Refused (not_accepting) while Settings pauses new-entry requests, unless this account may create entries itself. For someone or something with no Wikidata item, leave out qid. With qid, the entry is linked to that item, and after approval Wikidata keeps up to date whatever you did not write (and any field in let_wikidata_manage). Refused, naming the entry, when one is already on the item. A merged-away QID is refused (409 qid_merged), naming the item Wikidata kept in wikidata_item: propose on that one. Sending the same proposal again within 15 minutes answers with the first one. note tells the reviewer why. Audited. Dry run by default: it names the entries already on the item, a short name already taken or held by a site redirect (short_is_redirect), and handles already on another entry. Related entries link themselves: when it is approved, this entry and the other new entries this account proposed within a day link each other both ways on the first plain-text mention of each title, so write names as plain text and file no follow-up to add links; the dry run lists them (related_entries, links_on_approval).
Inputs: title (required), qid, note, short, +6 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
propose_wikidata_changesPropose several changes to one Wikidata item, as one groupAIdempotentInspect
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.
Inputs: qid (required), kind (required), changes (required), refile, +2 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
propose_wikidata_correctionPropose a Wikidata correctionAIdempotentInspect
Propose a correction to a Wikidata statement (Console → Wikidata → Review), for an administrator to approve and make. The item may be one no entry links (an event, say, which VH has no entry for): every statement on it is then read live, as one outside the catalog is, its card on Review says “Item not on VH”, and it takes any change but a deprecation or a merge (refused 422 qid_not_linked). It is filed as curated by your account and this key, and only proposes: nothing is written to Wikidata, and this server cannot approve or make an edit. Trusted editors and administrators may; a trusted editor’s account files at most 200 a day (UTC), all its keys together. set_value / remove / move one statement (its GUID, and the value you saw) on any property, P31 included — on one outside the catalog the site reads the statement live, the new value is as value below takes it, and a move is only between two properties of one datatype — or merge two items; evidence.why is required, and evidence.summary is the edit summary you would like (never naming this site). The kind says why: superseded (the subject renamed, or a newer value), duplicate (a duplicate statement), update (anything else you curate), or one of the format kinds. Or deprecate a value: the property and the value, a reason (an item id: one of the suggested reasons, else an instance of "reason for deprecated rank" on the write wiki) and an optional source page that says why, which the site loads itself (https, a public address); the site finds the statement and writes the evidence. Two kinds: suppressed, a value an editor took off VH that Wikidata still states (Console → Wikidata → To judge), whose evidence is that removal, so it takes none from you and is refused (not_suppressed) while VH still lists the value; or dead_account, an account the platform itself shows deleted, suspended or terminated, on a property of the platform catalog (property_not_allowed otherwise), whether or not VH still lists it, with evidence.why required (what the platform shows) and evidence.summary optional; or wrong_subject, a value two items state where they say they are two subjects (Console → Wikidata → To judge, “One account on two subjects”, which list_wikidata_wrong_subject_pairs reads), deprecated on qid, the item it does not belong to, with belongs_to the item it belongs to: filed whether or not VH still lists it, only while both items state it and the site’s identity check still says they are two subjects (both read live, and again just before it is made), on a property of the platform catalog, with the reason the site picks (reason may be left out: “refers to different person”, Q35773207, on a human, else “refers to different subject”, Q28091153; another is refused wrong_reason) and evidence it writes itself (refused pair_not_refused, value_not_shared or item_gone, each with a message, when that no longer holds). set_rank deprecated (below) is held to the same rules. When an entry linking the item still shows the value, both dry runs and the answer say so ("Still listed on VH entry (…): …", still_listed, each handle with kept_by). What VH then does with it: a handle the Wikidata sync keeps (kept_by "wikidata") is taken off the entry by the sync once Wikidata ranks the statement deprecated and the handle-removal grace is out (sync_state → settings.handles: its hours and consecutive fetches, and the blanking guard); a handle a person keeps the sync never takes off, so take it off with update_entry_handles if the account is gone. Or change the item’s terms in one language (a Wikimedia language code; mul for a label or aliases, never a description), kind superseded, duplicate or update: set_label / set_description with value_seen the term as you read it (null when the item has none in that language) and new_value the new text, at most 250 characters ("" removes it); set_aliases with value_seen the aliases as you read them ([] for none) and add and/or remove lists. It is made only while the term is still what you read. Or add a statement on any property (add_claim, kind superseded or update): property and value — a string (text, an identifier, a web address, an item id, a Commons file), {"text","language"} for a monolingual text, "YYYY-MM-DD", "YYYY-MM" or "YYYY" for a date, or an amount or {"amount","unit"} (unit an item id) for a quantity, either with "lowerBound" and "upperBound" for its range (both or neither, the amount between them; e.g. {"amount":"17000","lowerBound":"17000","upperBound":"17099"} for a count shown rounded down as "17K") — with optional qualifiers ([{"property","value"}], the same kinds of value, or {"unknown": true} for a time of unknown value, as add_qualifier takes one), and a REQUIRED reference (but on a Commons file, an image, a logo or a coat of arms, which is documented on Commons and goes without one; a Commons file page is never a reference): {"url" (https; the site loads it; never a Wikimedia project’s page, wikidata.org and its old revisions included, which is refused with why: wikimedia_reference; Verified Handles’ own page, this site’s or verifiedhandles.org’s, an archive copy’s included, is filed with the warning own_site_reference: keep it only where Verified Handles is genuinely the source, else cite the page the subject published), and/or "stated_in" (an item id, P248 “stated in”: the work or database the claim is made in, for a source with no stable page of its own, such as YouTube, Q866), and/or "identifier" ({"property", "value"}: an external identifier in that work, such as P244 no97057848 beside stated_in Q13219454, Library of Congress Authorities, for a record with no page the site can load; refused bad_reference when the property is not an external identifier, format_mismatch when the value fails its format), "retrieved" (YYYY-MM-DD, not after today; today if left out), "title" (optional; else the page’s own), "language" (optional, an item id: the language of the work), "archive_url" (optional: a web archive’s https copy of "url", P1065 archive URL, which the site loads instead of the original, so a page that is gone, http or https, can still be cited) and "archive_date" (optional, YYYY-MM-DD, P2960: the day it was archived, read from a web.archive.org or archive.today address when left out)}; the dry run shows the reference as the write wiki will get it (reference_snaks). The site reads each property’s datatype on the write wiki and refuses one it cannot write (datatype_unsupported); an identifier of digits alone may be sent as a JSON number and is filed as its digits, but only up to 9007199254740991: past it (a 64-bit id, such as a Discord server ID) JSON has already rounded it, so it is refused with a message saying to send it as a string; a text or identifier value (add_claim, supersede, set_value) that fails the property’s format constraint (P1793, read on the write wiki) is refused (format_mismatch, with pattern). Or add a reference to a statement (add_reference: property, statement_guid, optionally value_seen, and reference), or replace one of its references (replace_reference: also reference_hash, the hash of the one it replaces); each is made only while the statement, and the reference replaced, are still as you read them. Or change a statement’s qualifiers or rank (property, statement_guid, optionally value_seen): add_qualifier with qualifier {"property","value"} (any property, the same kinds of value: a dated start, end or point in time included, or {"unknown": true} for a time of unknown value — an end time no source dates, sent as Wikidata’s “unknown value”), change_qualifier with qualifier and qualifier_hash (the one it replaces), remove_qualifier with qualifier_hash; set_rank with rank preferred, normal or deprecated (deprecated needs a reason, checked as a deprecation’s is, and shows the same "Still listed" line). A preferred rank (set_rank, or add_claim with rank: "preferred") outranks the property’s normal values, so Wikidata stops counting them as current: when it would, the site names them ("Makes not current: …", makes_not_current) and refuses it (rank_choice_required) until you choose outranked: "end_date" end-dates each on end_date (YYYY-MM-DD, YYYY-MM or YYYY, not after today, or {"unknown": true}), filed as steps before it in one group; "keep_normal" makes it preferred and leaves them normal with no end time, for a value still true but less precise (Help:Ranking: a city of birth, Houston, preferred beside its country, United States, left normal); or "leave_normal" leaves them current and sets no preferred rank. A series of point-in-time values (a follower count P8687, a population, a revenue: each with a point in time, P585, and no start or end time; or a software version P348, each release with its publication date, P577, and no start or end time) is the exception: the newer value takes the preferred rank and the older ones stay normal with no end time, as Wikidata’s convention for such a series has it, without a choice (the dry run still names them in makes_not_current); an older value of the same account (the same identifier qualifier: P6552, P4033…), or an older release, that is preferred itself goes to normal too, a set_rank step after it, with its “most recent value” (P7452 Q71533355) removed first, and is named there as well — another account’s preferred count is left alone; "point_in_time" asks for that by name, and is refused (not_point_in_time) when one of them is not such a value. Or file the superseded bundle (action supersede, kind superseded): the statement you name end-dated on date, and a new statement of value on the same property at preferred rank with a start time of date (date {"unknown": true}: an end time of unknown value, and no start time), optional qualifiers and a REQUIRED reference, two steps of one group made in order (outranked / end_date for any other value it would outrank). A rebrand’s new logo is that bundle on the logo image property (P154 on www.wikidata.org; test.wikidata.org’s own is P95469) with value a Commons file name, found with search_commons_images: a file not on Commons is refused (file_not_found, “No logo on Commons yet: upload it there first, then propose it here.”, with Commons’ upload_url) and nothing is filed. Each is made only while the statement, its qualifiers and its rank are as you read them. Or move a statement to another item (move_to_item), or copy it there (copy_to_item; the same, leaving it where it is), kind superseded, duplicate or update: qid, property, statement_guid and value_seen name the statement, other_qid the item it goes to (never the same one). The site reads it live and files, on that item, a new statement with its whole value (a quantity’s range included), its qualifiers and its references exactly as read (kept as evidence.references_before), at normal rank; a move adds the removal of the statement, two steps of one group made in order, the removal only once the copy is made and only while the statement is still exactly as read. A reference that cites a Wikimedia page is never copied: the statement is refused (wikimedia_reference, naming those references by hash) unless you give a reference (an addition’s shape) to take its place; one given anyway is added after those read. Refused when that item already states the value (already_listed, a quantity inside a range stated included) or a proposal to add it is open (already_proposed). The dry run shows each step and the whole new statement as the write wiki will get it (statement). A proposal on a statement that already has an open correction of the same thing (the value, the rank, the same qualifier property, the same reference), or the site’s own suggestion, takes its place: the dry run names each one (replaces, their ids, and a line in warning, "Replaces #772 (dead_account, deprecate, reason Q1193907)."), and the answer gives the row it filed (ids) and those it replaced (replaced). A person’s open correction of the same change (the same statement, action, value and new property) is taken in as it stands 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, “Takes in the open change #3329 (…)”) and nothing new is filed for it. One that writes it otherwise (another reference, qualifier or rank) refuses the proposal (409 already_proposed, with its id, a group’s step and a message), dry run or not, and nothing is filed: leave the change out, or have that row dismissed first. A reference cited by a web archive’s copy and one cited by the original with that copy as its archive_url are the same reference. One beside a person’s open change to something else on the statement (another qualifier, a reference, the value beside a qualifier) closes nothing: it is joined to that open change as its next step, one group made in that order and one card on Review (the dry run’s joins, the answer’s joined and group_id, and a line in warning, "Joined to the open change #4364 (…) as its next step: one proposal, made in that order."; where the open change sets the value, the line says this one, checked against the old value, stops once that one is made and wants proposing again then). To withdraw a correction without filing one in its place, use dismiss_wikidata_correction. A change a person dismissed is not filed again while Wikidata says the same thing: the same kind and action on the same statement, with the same value seen, new value and new property and the whole value written (a quantity’s range, a new statement’s qualifiers and rank) and the same reference (the day retrieved aside), is refused (409 dismissed, the dry run included, with dismissed_id, dismissed_at and a message); send it again with refile: true to file it anyway (its evidence and the audit name the dismissed row). Any other change on that statement is filed as usual, so a dismissed row with the wrong reason, or a weak reference, is corrected by proposing the right one. Audited. Dry run by default: a deprecation’s, a term’s, a statement’s, a reference’s, a qualifier’s or a rank’s dry run has the site check it all and show what it would file (each step of a group, and the rank warning, included). The owner’s Wikidata conventions are checked as it is filed (each refusal’s message says what is wrong and its suggestion exactly what to change, and nothing is filed). Refused: a new YouTube channel ID statement (P2397) without its title as a “subject named as” (P1810) qualifier (channel_without_title); a YouTube handle (P11245) whose P2397 qualifier names a channel the item does not state and no earlier change of the proposal adds (handle_without_channel); a reference whose url is a web archive’s copy (web.archive.org, archive.today: archive_as_reference; give the original page as the url and the copy as archive_url); an add_claim whose value, and each qualifier it gives, the item states already (claim_already_present: add the reference to that statement instead, add_reference with its GUID); a set_value of a Bluesky handle (P12361) on a statement with no Bluesky DID (P12409) when the proposal adds none (bluesky_handle_without_did: add it with an add_qualifier in the same group); kind superseded filed as a set_value, which writes over a value that was true once (superseded_in_place: propose the supersede bundle, the old value ended and the new one added). Filed with a warning instead (warnings, each with its code, step, message and suggestion, and in warning; kept on the row for the reviewer): a YouTube count whose range is centred on its amount where YouTube rounds down (range_not_rounded_down: “1.42M” is 1420000 to 1429999); a YouTube count whose range starts at its amount but is wider than YouTube’s rounding to three significant figures (range_too_wide: “1.7M” is 1700000 to 1709999, not to 1799999); a round count on a platform that shows counts rounded (YouTube, TikTok, Instagram, Snapchat, X) filed as exact (rounded_count_exact: “399.1K” is 399100 to 399199); a new count at normal rank that is its account’s newest, where the item keeps each account’s newest count preferred or has none preferred (count_not_preferred); a preferred follower count that makes another account’s newest count not current (preferred_outranks_other_accounts); a new preferred count while an older count of the same account stays preferred, on the item or by another open proposal, which it names (same_account_still_preferred); a preferred count demoted with no newer one for its account in the proposal (depends_on_other_proposal: propose the two together); an account deprecated beside its successor, which wants an end time instead (replacement_deprecated); a start or end time (P580, P582) on the day it is proposed or its reference retrieved, which no source dates (made_up_date: Wikidata wants an end time of unknown value, {"unknown": true}, unless a source dates it); a reference stated in (P248) an item that is not the platform of the account it supports, or stated in a platform’s item (the YouTube API, Q8056784) for an identifier that is none of that platform’s, such as an Apple Music artist ID linked from a video (stated_in_mismatch, on www.wikidata.org: cite the page you read it on); a second value at normal rank of a single-best-value property (P2013, P7085, P19…) beside another normal one and none preferred (single_best_second_normal, on www.wikidata.org); an account statement that carries a reference, removed (remove_with_reference: deprecate another person’s account with reason Q35773207 instead, so no import adds it again; a reference imported from Wikimedia, P143, alone is no source and is not warned); a value deprecated as about someone else (“refers to different person” Q35773207 or “refers to different subject” Q28091153) on a statement with no reference, or only one imported from Wikimedia (P143), and none added by the proposal (unsourced_deprecated_remove: “This value has no source: a value about someone else is removed, not deprecated.” Remove it instead; deprecate only a wrong value a source states, which a removal would let be added again); aliases added in one language that are the item’s default (mul) aliases already (alias_duplicates_mul); a reference titled with a platform’s own page title, such as “TikTok - Make Your Day” (generic_reference_title; its suggestion keeps a stated_in you give); a reference stated in a class of accounts, such as “Twitch channel” (Q99869602), rather than the platform, Twitch (Q4555537) (stated_in_not_a_source, www.wikidata.org); a dead account deprecated while the item states another current value of its property (other_current_values), and a value deprecated as “changed username”, “redirect” or “cannot be confirmed by other sources” while the item or a VH entry on it holds another value of its property (outdated_not_wrong): each was right once, so end it (P582) rather than deprecate it; a new YouTube handle (P11245) that is not, case aside, the handle this site’s handle checker last saw its P2397 channel with (handle_differs_from_channel: the handle is what YouTube shows after the @, not the channel’s title); and a point in time, start or end time added to an award (P166) or nomination (P1411) statement that has one with another value already (second_date_on_statement: each year is a statement of its own; www.wikidata.org); a reference that is Verified Handles’ own page, this site’s or verifiedhandles.org’s (own_site_reference: keep it only where Verified Handles is genuinely the source); a reference on an account or official website (P856) statement whose url is a social profile page, read by the platform catalog’s templates: the account itself, such as an X username cited by its x.com page or a YouTube channel by its own page or /about tab, or another profile cited as the source, such as a YouTube /about page for an X or Instagram account or the website (profile_reference: cite a page independent of the account, the official website or a news article; a post, a video and any other page are never warned; on an account of a platform the site knows, such a reference is not filed as given: the statement is filed stated in the platform’s item instead, see reference); and a new TikTok, Instagram, Threads, Twitch or X account statement (P7085, P2003, P11892, P5797, P2002) with no “subject named as” (P1810) qualifier (missing_display_name: add the account’s display name as the platform shows it); and a duplicate removed (kind duplicate) whose value has capitals, on a platform that ignores letter case (X, Instagram, TikTok, Threads, a YouTube handle, Twitch, Kick, GitHub, Reddit, Facebook), while the copy the item keeps is all lower case (removes_cased_copy: the casing the account shows is the copy to keep, so remove the lowercase one instead, its references and qualifiers moved onto the other first, unless the account really is all lower case); and an account deprecated (set_rank deprecated, or a deprecation) as not the subject’s (“refers to different person”, “refers to different subject”, “incorrect value”, “incorrect identifier value” or “conflation”) while follower counts of it (P8687 qualified with one of its identifiers: P6552 or P2002 on X, P2397 or P11245 on YouTube…) stay current on the item, or such a count deprecated while its account stays current (account_counts_apart, naming them, and any open proposal that deprecates one of them apart: they stand or fall together, so propose the account’s set_rank deprecated and each count’s in one propose_wikidata_changes call, which takes those open proposals into its group). 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.
Inputs: qid (required), kind (required), action (required), add, +24 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
reject_applicationDecline an applicationADestructiveInspect
Decline an open application with a reason and an optional note; the applicant is emailed both, and the note goes on its thread. Cannot be undone (they may apply again). Audited. Dry run by default; the real run needs confirm set to the application’s id.
Inputs: reason (required), application_id (required), note, confirm, +1 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
report_entryReport an entryAInspect
Report an entry to the Verified Handles team, as its page’s “Report” form does: for a person to decide: delete, merge, image rights, wrong information. Reason image names the image it is about (media_id, one of the images the entry shows) and needs a note saying who owns it and what should change. Reason image_link is about where an image links (only for an image with a link — get_entry’s images[].link); media_id names which, else the first with one, and the report keeps the link as it is now. To delete or merge an entry, report it as incorrect or other with a note naming the entry to keep. It lands in Console → Reports. Audited. Dry run by default.
Inputs: entry (required), reason (required), note, dry_run, +1 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
retract_my_submissionRetract my own submissionAIdempotentInspect
Withdraw one of this key’s own account’s submissions while it is still open (waiting for a reviewer, or for your answer): no reviewer acts on it after, and it cannot be reopened. Only your own, whatever the key’s role. Audited. Dry run by default: it says whether the submission is yours and still open.
Inputs: id (required), dry_run. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
review_submissionDecide a submissionADestructiveInspect
Decide one waiting submission (list_review_queue, or a quick proposal from list_applications with tab "proposals"): approve a proposed change or new entry (it is applied as an edit; one made on an earlier version of the entry is rebased onto it and applied, and only a change that clashes with a later edit of the same field or handle is answered with the clashes, not applied: approve again with resolve), reject it or mark it spam (with an optional note to the submitter), or resolve a report (with an optional reply). A claim whose entry another account already holds (list_review_queue’s entity_claimed_by_other) and that is moot — the same person on a second account, a check that failed — is better closed (decision "close": superseded, no email) than rejected, which emails them that it “wasn’t approved”. Approving a claim held for an admin lists the other accounts’ pending claims on the entry; close_other_claims closes them with it, no email. An application (one waiting on the applicant too) is decided through the Applications queue, as approve_application, reject_application (needs reason) and mark_application_spam do: approving records its assessment as it stands, and rejecting it or marking it spam needs confirm set to its id. Audited. Dry run by default.
Inputs: decision (required), submission_id (required), note, reason, +4 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
revoke_api_keyRevoke an API keyADestructiveIdempotentInspect
Revoke an API key: anything using it stops working at once, and it cannot be brought back (its owner makes a new one). One of your own account’s keys, or — with sub, and the permission to manage users — one of another account’s. The dry run lists the account’s keys (never more than a key’s public prefix) and says if it is the key this call is made with. Audited. Dry run by default; the real run needs confirm set to the key’s id.
Inputs: key_id (required), sub, confirm, dry_run. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
search_commons_imagesSearch Wikimedia CommonsARead-onlyInspect
Search Wikimedia Commons for an image to put on an entry, as the editor’s image picker does. An exact file name finds that file first, even one uploaded minutes ago. Each hit has a token: pass it to set_entry_image as commons_token.
Inputs: query (required). Returns: results
search_entriesSearch entriesARead-onlyInspect
Search the entries as the site search does: words match titles, subtitles and descriptions; a Wikidata QID finds the entries linked to it; a VHID finds that entry and the entries that link to it.
Inputs: query (required), limit, offset. Returns: limit, query, total, offset, +2 more
set_article_heroSet an article’s hero imageADestructiveIdempotentInspect
Set the image at the top of an article, and its alt text (what it shows, for a reader who cannot see it), as a save does: an uploaded image’s media id (upload_image, upload_image_from_url, or media_catalog), or null to take it off; or, for a data story, a chart the site draws as the hero (its figures shown as a table under it). One or the other: a picture replaces a chart. Audited with the key and the tool. Dry run by default.
Inputs: article (required), alt, chart, dry_run, +2 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
set_entry_gallerySet an entry’s galleryADestructiveInspect
Set the images an entry shows after its lead image: the whole ordered list of media ids (from media_catalog or get_entry), replacing the gallery; [] empties it. At most 5 (6 images in all with the lead), each once, never the lead itself (set_entry_image sets that). An image taken off loses its link; links sets or clears the link of an image in the list (needs Link images). A live edit, audited. Dry run by default. To ask a reviewer instead, use propose_entry_change.
Inputs: entry (required), media_ids (required), links, dry_run, +3 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
set_entry_imageSet or clear an entry’s imageADestructiveInspect
Put an image on an entry — one already on the site (media_id, from media_catalog or get_entry) or a Wikimedia Commons file (commons_token, from search_commons_images) — or take the image off (clear: true). A new image starts with no link; link sets the address the image opens on the entry page instead of the full-screen viewer ("" clears it), which needs Link images. A live edit, audited. Setting the image yourself takes it from the Wikidata sync. Dry run by default. To ask a reviewer instead, use propose_entry_change.
Inputs: entry (required), link, clear, dry_run, +5 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
set_wikidata_ownershipHand fields or handles to Wikidata, or take them backADestructiveInspect
Say who manages an entry’s fields and handles. relinquish_* hands them to the Wikidata sync (the next sync refreshes them, and a relinquish queues one); takeover_* takes them back, so the sync leaves them alone. release_held_handles lets the sync add back handles that were held back after a removal. A live edit, audited. Dry run by default. To ask a reviewer instead, use propose_entry_change.
Inputs: entry (required), dry_run, summary, idempotency_key, +6 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
update_article_draftEdit an articleADestructiveIdempotentInspect
Save a new version of an article, as the console’s Save does: only the fields given change, over the article’s own (null clears one). A draft changes at once. A live (or scheduled) article changes at once for a key whose account may publish (modified: true moves its visible “Updated” date); for any other key the save waits for a publisher, and readers keep the words they see now. The slug of an article that has been published changes only with change_article_slug. Audited with the key and the tool. Dry run by default: it shows what changes, the cleaned HTML of a new body, its links and what the allowlist took out, and whether the save would wait.
Inputs: article (required), dek, body, slug, +9 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
update_entriesEdit many entries liveADestructiveInspect
Live edits to up to 25 entries in one request, each as update_entry_fields and update_entry_handles make one (the text fields, handles added and removed): a new revision each, audited with one batch id. Whether this key may edit each entry live is decided entry by entry, as for one edit (the dry run’s may_edit_live). By default each edit stands alone and the answer gives each one’s outcome; with atomic: true, any refused edit means none is made. Dry run by default: it reads each entry and lists what would change. The real run needs confirm set to the batch digest the dry run names. To ask a reviewer instead, use propose_entry_changes.
Inputs: edits (required), atomic, confirm, dry_run, +2 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
update_entry_fieldsEdit an entry’s textADestructiveInspect
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.
Inputs: entry (required), bio, short, title, +11 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
update_entry_handlesAdd or remove handlesADestructiveInspect
Add handles to an entry, remove them, or move some to the front — a live edit. Only the handles named are sent (add_handles / remove_handles), and the server applies them to the entry’s list as it is when it saves: an added handle goes at the end, one the entry has already, or one to remove that it has not, changes nothing (the answer’s handle_ops says which), and nothing is read first, so a handle someone else saved meanwhile is never undone. first moves the handles it names to the front, in its order, the others keeping theirs: the tool reads the list and sends it whole, against the revision it read (a save in between is refused as a conflict; run it again), and a handle in first the entry has not is refused. A handle you remove that the Wikidata sync supplied is held back so the sync does not bring it back. Dry run by default. To ask a reviewer instead, use propose_entry_change.
Inputs: entry (required), add, first, remove, +4 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
upload_imageUpload an image fileAInspect
Upload an image file you hold, sent as base64, with its licence, credit and source (the editor’s “upload a file”), stored as a new image — a lossless WebP at the file’s full resolution with its colour profile kept and every other metadata (EXIF, XMP, IPTC) dropped: at most 70 MB of file (its base64 is a third larger: up to 94 MB, which the site takes whole). POST /api/media (multipart, with this key) takes a file of the same 70 MB. The image is public at /img/w/…/ once stored, before any review — unless you set hold: true, which stores it held for a proposal: /img serves it only to you and to reviewers (never cached), it is in no list, and only your own proposal may name it, until a reviewer approves that proposal and releases it. A rejected or withdrawn proposal leaves it held, never deleted. The real run answers its mediaId: pass it to propose_entry_change as image_media_id to propose it for an entry. Audited, with the file name. Dry run by default; every run needs confirm_rights: true.
Inputs: content (required), license (required), filename (required), confirm_rights (required), +4 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
upload_image_from_urlUpload an image from a web addressAInspect
Upload an image the site fetches from an https address (the editor’s “from a web address”), with its licence, credit and source, stored as a new image (a lossless WebP at its full resolution, colour profile kept, other metadata dropped). The image is public at /img/w/…/ once stored, before any review — unless you set hold: true, which stores it held for a proposal: /img serves it only to you and to reviewers (never cached), it is in no list, and only your own proposal may name it, until a reviewer approves that proposal and releases it. A rejected or withdrawn proposal leaves it held, never deleted. The real run answers its mediaId: pass it to propose_entry_change as image_media_id to propose it for an entry. Refused (url_upload_disabled) while an admin has switched uploads from a web address off. Audited, with the address. Dry run by default; every run needs confirm_rights: true.
Inputs: url (required), license (required), confirm_rights (required), hold, +3 more. Returns: A dry run (`dry_run: true`): what the change would be and the exact request it…
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
OSINT lookups: usernames, social profiles, phones, domains, IPs, crypto wallets and companies.
Read public social profiles and posts, and search videos, news and trends.
Machine-readable entity discovery with provenance, trust and verified source evidence.
Look up creators on lookmybio: public bio pages, their links and published blog posts.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables users to look up a person's public GitHub, Bluesky, personal site, Substack, and X profiles from their full name and company domain, with status and confidence per platform and no emails or phone numbers.1294 npmMIT
- AlicenseAqualityDmaintenanceChecks username availability and retrieves account information across major social media platforms including YouTube, TikTok, Threads, X (Twitter), and Instagram, perfect for brand name qualification and competitive research.1269 npm1MIT

bluepages-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables looking up Ethereum address mappings to Twitter/X and Farcaster identities, with tools for checking and retrieving identity data.1MIT- AlicenseAqualityBmaintenanceResolves TikTok handles or company domains to brand accounts, returning follower, like, video counts, verification status, and more.1339 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.