storychoose_list_stories

What it does

storychoose_list_stories is a read tool for StoryChoose (storychoose.com), where people keep original bedtime stories starring their children, read aloud in natural voices. It lists the bedtime stories in one person's StoryChoose library. It changes nothing.

Send an optional limit to set how many items come back. The default is 10 and the accepted range is 1 to 50. The result is a stories array. Each entry carries id, title, created_at, favorite, language and url. The call is idempotent, so repeating it with the same arguments returns the same listing rather than creating or changing anything.

When an assistant should call it

Call it when the person asks what stories are in their library, wants to find a favorite, or needs a story id before calling storychoose_get_story or storychoose_favorite_story. It is the right first step when you need to look at the library before acting on a specific story.

Use it to answer questions about the library itself: which stories exist, what language a story is in, when it was created, or whether it is marked as a favorite. If the person asks about characters instead, use storychoose_list_characters.

Do not call it to change a favorite; storychoose_favorite_story handles that. This tool only reads the library.

Inputs and an example call

The only input is limit, an optional integer from 1 to 50. Omit it to get the default 10 items. The request below asks for 10 items from the account connector at https://onelifevibe.com/mcp.

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"storychoose_list_stories","arguments":{"limit":10}}}

That connector needs the person's OneLifeVibe sign-in (OAuth 2.1 with PKCE) and the scope olv.read. The person must also have signed in to storychoose.com with OneLifeVibe once; otherwise the tool answers not_linked. Meta Muse is set up today with the client onelifevibe-muse. Other MCP clients reach the no-account tools through the free connector. The Platform API registry lists this tool in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it today because it acts on one member's own data.

What comes back

A successful call returns a stories array. Each item has id, title, created_at, favorite, language and url. Use id with storychoose_get_story or storychoose_favorite_story when the next step needs a specific story.

The array holds at most the number you asked for with limit, up to 50. The call is idempotent: the same limit returns the same listing. Nothing in the library is modified by the call.

Errors, limits and safety

If the person has not signed in to storychoose.com with OneLifeVibe, the tool returns not_linked. Ask them to sign in at storychoose.com with OneLifeVibe, then retry. A platform key gets 501 world_tools_unavailable for this tool today. Use the account connector at https://onelifevibe.com/mcp with OAuth 2.1 with PKCE and scope olv.read instead.

A limit below 1 or above 50 is outside the accepted range. Omit limit or send an integer from 1 to 50. The tool is read-only and not destructive; it cannot add, edit or remove stories. It only returns the library of the person whose OneLifeVibe sign-in is in use.