Wikidata

Get Entity

get_entity

Read-onlyIdempotent

Get full Wikidata entity by ID (e.g., "Q42" for Douglas Adams, "Q5" for human, "Q1764" for Budapest). Returns labels, descriptions, aliases, claims/statements (properties and values), sitelinks, and the revision the data came from — lastrevid plus the modified timestamp — so live statements can be pinned to a specific edit. Pass "language" (comma/pipe-joined for several) to get labels/descriptions in languages other than English, side by side. For checking several ids at once, use get_entities instead of looping this.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Wikidata entity ID (e.g., "Q42", "Q937", "P31")
`language`	No	Language code(s) for labels/descriptions/aliases — a single code (e.g. "ka") or a comma/pipe-joined list to compare several at once (e.g. "ka,ru,en"), which returns every requested language's label side by side in one call — the shape needed to decide whether two records in different languages describe the same entity. Default "en". Falls back to "en", then to Wikidata's language-neutral "mul" label, for any requested language the entity has no label in — Q42 (Douglas Adams) has no English label at all, only a "mul" one. When the name came from "mul" it appears under a "mul" key in the labels map, so you can tell where it came from.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Wikidata entity ID
`type`	Yes	Entity type (e.g., 'item', 'property')
`label`	Yes	English label for the entity
`claims`	Yes	Property claims/statements (up to 30 properties, 5 values each)
`aliases`	Yes	List of alternative names
`modified`	Yes	UTC timestamp of that revision (ISO 8601)
`lastrevid`	Yes	Revision id these statements were read at, for pinning the answer to a specific edit
`description`	Yes	English description of the entity
`revision_url`	Yes	Permalink to that exact revision on wikidata.org
`wikipedia_en`	Yes	English Wikipedia article title if available
`sitelinks_count`	Yes	Number of Wikipedia/sister project links

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedInput schema / properties / language / description

Previous value: -"Language code(s) for labels/descriptions/aliases — a single code (e.g. \"ka\") or a comma/pipe-joined list to compare several at once (e.g. \"ka,ru,en\"), which returns every requested language's label side by side in one call — the shape needed to decide whether two records in different languages describe the same entity. Default \"en\". Falls back to \"en\" for any requested language the entity has no label in."New value: +"Language code(s) for labels/descriptions/aliases — a single code (e.g. \"ka\") or a comma/pipe-joined list to compare several at once (e.g. \"ka,ru,en\"), which returns every requested language's label side by side in one call — the shape needed to decide whether two records in different languages describe the same entity. Default \"en\". Falls back to \"en\", then to Wikidata's language-neutral \"mul\" label, for any requested language the entity has no label in — Q42 (Douglas Adams) has no English label at all, only a \"mul\" one. When the name came from \"mul\" it appears under a \"mul\" key in the labels map, so you can tell where it came from."

Changed2 schema fields changedSep 9, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "id": "Q42"
-  },
-  {
-    "id": "Q1764"
-  }
-]New value: +[
+  {
+    "id": "Q42"
+  },
+  {
+    "id": "Q162887",
+    "language": "ka,ru,en"
+  }
+]

addedInput schema / properties / language

Added value: +{
+  "description": "Language code(s) for labels/descriptions/aliases — a single code (e.g. \"ka\") or a comma/pipe-joined list to compare several at once (e.g. \"ka,ru,en\"), which returns every requested language's label side by side in one call — the shape needed to decide whether two records in different languages describe the same entity. Default \"en\". Falls back to \"en\" for any requested language the entity has no label in.",
+  "type": "string"
+}

Changed4 schema fields changedAug 22, 2026

addedOutput schema / properties / lastrevid

Added value: +{
+  "description": "Revision id these statements were read at, for pinning the answer to a specific edit",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / modified

Added value: +{
+  "description": "UTC timestamp of that revision (ISO 8601)",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / revision_url

Added value: +{
+  "description": "Permalink to that exact revision on wikidata.org",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "type",
-  "label",
-  "description",
-  "aliases",
-  "claims",
-  "sitelinks_count",
-  "wikipedia_en"
-]New value: +[
+  "id",
+  "type",
+  "label",
+  "description",
+  "aliases",
+  "claims",
+  "sitelinks_count",
+  "wikipedia_en",
+  "lastrevid",
+  "modified",
+  "revision_url"
+]

First observedJun 26, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description discloses the full return shape: labels, descriptions, aliases, claims/sitelinks, plus lastrevid and modified timestamp, and explains the language fallback behavior. Even with readOnly/openWorld/idempotent annotations, it adds significant behavioral detail.

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

Conciseness5/5

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

The description is compact, front-loaded with the primary purpose, and uses only well-chosen supporting details: examples, response fields, language behavior, and the sibling-tool pointer. No filler.

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 read-only lookup tool with a single required parameter and a rich output schema, the description covers everything an agent needs to call it correctly, interpret results, and choose the right sibling tool.

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

Parameters3/5

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

The input schema already documents both parameters thoroughly (100% coverage), including language code format and fallback behavior. The description reinforces the semantics but does not add much beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Get full Wikidata entity by ID,' with concrete examples (Q42, Q5, Q1764). It clearly distinguishes the singular-entity purpose from the plural get_entities sibling tool.

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

Usage Guidelines5/5

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

Explicitly tells the agent when to use this tool versus an alternative: 'For checking several ids at once, use get_entities instead of looping this.' This gives a direct selection rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Wikidata tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.