ShapelessAI

Pull one more ring of a node

identity_expand

Destructive

SPENDS CREDIT. Grow one node by one expansion: profile, posts, sponsors, ads, creators, metrics or labels. A fresh expansion answers costUsd 0 unless force. budgetUsd 0.01 to 2 engine USD (default 0.5) is held on the wallet first; only what the pull cost is charged. Price it first with identity_estimate. Needs the write scope.

Input Schema

Name	Required	Description
`node`	Yes	A node id: person:<uuid>, account:<uuid>, organization:<uuid> or asset:<platform>:<postId>. identity_search finds one; a resolve's anchor is one.
`force`	No	Pull even when fresh (profiles for a day, posts by the account's own posting rhythm, sponsors, ads, creators and labels for a week), and the whole posts range rather than only the unread gaps.
`since`	No	posts only: oldest publish day, YYYY-MM-DD (default now minus sinceMonths).
`until`	No	posts only: newest publish day, YYYY-MM-DD (default now).
`maxItems`	No	posts only: the most posts one pull lands, 25 to 1000, default 300.
`budgetUsd`	No	Engine USD, 0.01 to 2, default 0.5.
`expansion`	Yes	profile: an account's profile, a person's accounts' profiles, an organization's site, accounts and logo. posts: an account's posts with metrics (since/until/sinceMonths/maxItems apply). sponsors: brands that paid an account. ads: an organization's ads from the ad libraries. creators: an organization's creators (paid, partners, and the ones its accounts feature), cheapest evidence first. metrics: a fresh snapshot of one post (asset). labels: what a person or organization is (category, niches), read by a model; also what identity_similar ranks by.
`sinceMonths`	No	posts only: 1 to 36 months back, default 12.

Output Schema

Name	Required	Description	Default
`error`	Yes
`nodes`	Yes
`pulls`	Yes
`anchor`	Yes
`status`	No
`costUsd`	Yes
`holdUsd`	No
`summary`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / expansion / description

Previous value: -"profile: an account's profile, a person's accounts' profiles, an organization's site, accounts and logo. posts: an account's posts with metrics (since/until/sinceMonths/maxItems apply). sponsors: brands that paid an account. ads: an organization's ads from the ad libraries. creators: every creator an organization paid. metrics: a fresh snapshot of one post (asset). labels: what a person or organization is (category, niches), read by a model; also what identity_similar ranks by."New value: +"profile: an account's profile, a person's accounts' profiles, an organization's site, accounts and logo. posts: an account's posts with metrics (since/until/sinceMonths/maxItems apply). sponsors: brands that paid an account. ads: an organization's ads from the ad libraries. creators: an organization's creators (paid, partners, and the ones its accounts feature), cheapest evidence first. metrics: a fresh snapshot of one post (asset). labels: what a person or organization is (category, niches), read by a model; also what identity_similar ranks by."

changedInput schema / properties / force / description

Previous value: -"Pull even when fresh (profiles and posts are fresh for a day, sponsors, ads, creators and labels for a week), and the whole posts range rather than only the unread gaps."New value: +"Pull even when fresh (profiles for a day, posts by the account's own posting rhythm, sponsors, ads, creators and labels for a week), and the whole posts range rather than only the unread gaps."

AddedOct 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare a destructive, non-read-only, open-world write. The description adds substantial context beyond them: it spends credit, holds budgetUsd on the wallet first, charges only actual pull cost, gives fresh expansions cost 0 unless force, and states the write scope requirement. That is rich disclosure of cost, side effects, and auth preconditions for a destructive tool.

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

Conciseness4/5

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

The cost warning is front-loaded ('SPENDS CREDIT.') and most sentences are dense with useful distinctions. The freshness-window parenthetical is somewhat compressed, but every sentence carries operational information and nothing is wasted.

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 destructive, credit-spending expansion tool with an output schema already defined, the description covers the critical unknowns: cost behavior, budget reservation, force semantics, auth scope, and expansion meanings. No essential calling information is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description goes beyond the schema by explaining that fresh expansions cost 0 unless force, how the budget hold works, and that creators are ordered 'cheapest evidence first' – meaningful semantics not fully captured by the per-parameter descriptions.

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?

States a specific verb and resource ('Grow one node by one expansion') and enumerates the seven expansion types, so an agent knows exactly what this tool produces. It also names the related pricing sibling (identity_estimate), distinguishing it from estimate/preview tools without opening either schema.

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

Usage Guidelines4/5

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

Explicitly says 'Price it first with identity_estimate' and 'Needs the write scope,' giving a clear precondition and alternative. It also implies the force/freshness condition for when a re-pull is needed, though it does not state explicit cases when this tool should not be used.

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

All ShapelessAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.