datalens_embeddingsecrets_listList the embedding keys for a workbook, excluding private keys, to configure DataLens workbook embedding without exposing secrets.
The keys for embedding of a workbook, without their private keys.
| Name | Required | Description | Default |
|---|---|---|---|
| workbook_id | Yes | Workbook id. |
Changes observed during successful MCP inspections.
v0.122.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint/idempotentHint, so the safety profile is covered. The description adds a genuinely useful behavioral detail beyond annotations: returned keys omit their private keys, which tells the agent what it will and won't get back.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single compact clause with the key information front-loaded. It is a fragment rather than a full sentence, but every word earns its place and there is no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read-only list tool with no output schema, the description covers the core purpose but leaves gaps: no guidance on alternatives and no mention of which workbook-scoped key list gets returned. Adequate but with clear room to do more.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single workbook_id parameter is documented. The description only implies the workbook scoping ('of a workbook') and adds no syntax or format detail beyond the schema, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a clear verb (list) and resource (embedding keys for a workbook), and adds an informative qualifier that the keys exclude private keys. It does not, however, distinguish this list tool from its close sibling datalens_embeddingsecrets_get.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No indication of when to use this tool versus datalens_embeddingsecrets_get, datalens_embeds_list, or datalens_embeddingsecrets_create. The agent must infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.