Use it when listing mappings, resolving an external component or reviewing a draftId; use component_map to stage or apply changes. Returns entries, matches or draft evidence including proposed adapters and unmatched elements. Reads local stores without generating adapters or changing project files. Full schema: oods://schemas/component_map_read.input.json.

Inputs

Name Type Required Description
action "list" | "resolve" | "show" yes Choose list, resolve, show.
externalSystem string no For list: Filter mappings to a specific external system (e.g., 'team'). For resolve: External design system name (e.g., 'team'). Actions: list, resolve (required).
cursor string no Pagination cursor. Use the previous page's nextCursor to continue. When cursor or limit is provided, pagination defaults to 100 items per page. Actions: list.
limit integer no Page size for pagination. Omitting both cursor and limit preserves the legacy full-list response. Actions: list.
externalComponent string no Component name in the external system (e.g., 'Button'). Actions: resolve (required).
draftId string no Actions: show (required).

Outputs

The package ships no output schema for this tool.

A real call

Recorded by this site's tools run, step component-map-list, with the published OODS Foundry 0.11.0.

Its input:

{
  "action": "list"
}

Its result:

{
  "mappings": [],
  "totalCount": 0,
  "stats": {
    "mappingCount": 0,
    "systemCount": 0
  },
  "etag": "52e7a4e408afda59439e476264ff7c5d6d6ac0aedbf035f74a848c156eb5bf04"
}

The whole call, 1 KB of JSON