getUserMeta
Retrieve a single user metadata record by its meta_id. Used to verify the metadata row before performing updates or deletions.
Instructions
Get a single metadata record - Fetch a single usermeta record. Read-only.
Use when: fetching one metadata row by meta_id.
Required: meta_id.
Identity check before downstream writes: Before using this row's meta_id for any subsequent updateUserMeta/deleteUserMeta call, confirm the response's database and database_id fields BOTH match the parent record you intend to modify. The same database_id can exist across unrelated parent tables (users_data, list_seo, subscription_types, data_posts, etc.) - blindly passing a meta_id forward without verifying its (database, database_id) pair can silently corrupt or destroy data on an unrelated table. Optional database and database_id query params are accepted for documentation/intent — the actual verification is agent-side (compare message[0].database / message[0].database_id to what you expected before acting).
See also: listUserMeta (enumerate many).
Returns: { status: "success", message: [{...record}] } - the message array contains 1 record when found. Empty or HTTP 404 when not found.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| meta_id | Yes | ||
| database | No | OPTIONAL — your expected parent table name (e.g. `list_seo`). Accepted for intent documentation; verification is agent-side (compare `message[0].database` in the response). Recommended on any `getUserMeta` preceding a write to the users_meta table. | |
| database_id | No | OPTIONAL — your expected parent record PK. Same intent-documentation convention as `database`. Agent-side verification: compare `message[0].database_id` before acting on the row. |