Tools Reference
Complete reference for all 130+ tools available in BlokMCP. Tools are organized both by use case (what you want to accomplish) and by module (technical grouping).
How to Use This Reference
New to BlokMCP?
- Start with Browse by Category to find tools based on what you want to do
- Use conversational requests - you don't need to memorize tool names
- Check out Conversation Starters for practical examples
Looking for specific tools?
- Browse By Category for use-case organization
- Browse By Module for detailed API documentation
Understanding tool names:
fetch_*- List or search multiple items (e.g.,fetch_stories)get_*- Retrieve a single item by ID (e.g.,get_story)create_*- Create new items (e.g.,create_story)update_*- Modify existing items (e.g.,update_story)delete_*- Remove items (e.g.,delete_story)publish_*- Make content live (e.g.,publish_story)
Browse by Category
Use-case-based organization - Find tools based on what you want to accomplish:
Content Management
Create, update, publish, and manage stories and components.
What you can do:
- Create and edit stories
- Manage component schemas
- Publish and unpublish content
- Version control and history
- Story organization and folders
Tools included: Stories (18), Components (9), Component Folders (2)
Asset Management
Upload, organize, and manage media files.
What you can do:
- Upload images, videos, and files
- Organize assets into folders
- Search and filter assets
- Bulk asset operations
- Delete and manage asset lifecycle
Tools included: Assets (9), Asset Folders (4)
Workflows
Set up approval workflows, manage stages, and track progress.
What you can do:
- Create and manage workflows
- Configure workflow stages
- Track workflow changes
- Manage approvals
- Monitor content progression
Tools included: Workflows (4), Workflow Stages (5), Workflow Stage Changes (4), Approvals (3)
Data Sources
Manage key-value data stores and structured data.
What you can do:
- Create and manage datasources
- Add and update datasource entries
- Organize data for dynamic content
- Bulk data operations
Tools included: Datasources (5), Datasource Entries (5)
Collaboration
Manage team members, tasks, and discussions.
What you can do:
- Add and manage collaborators
- Assign and track tasks
- Create discussions on content
- Manage permissions and roles
Tools included: Collaborators (4), Tasks (5), Discussions (3), Space Roles (5)
Space Administration
Configure space settings, roles, and advanced features.
What you can do:
- View and update space settings
- Manage roles and permissions
- Configure branches
- Deploy changes
- Access space metadata
Tools included: Space (3), Space Roles (5), Branch Deployments (3)
Integrations
Set up webhooks, extensions, and field plugins.
What you can do:
- Configure webhooks for events
- Manage extensions
- Set up field plugins
- Monitor webhook activity
Tools included: Webhooks (5), Extensions (3), Field Plugins (3)
Browse by Module
Technical organization - Detailed API documentation for each module:
| Module | Tools | Description |
|---|---|---|
| Stories | 18 | CRUD operations, publishing, versioning |
| Components | 9 | Schema management, versioning, usage |
| Assets | 9 | Upload, organize, manage media |
| Asset Folders | 4 | Organize assets into folders |
| Workflows | 4 | Create and manage workflows |
| Workflow Stages | 5 | Configure workflow stages |
| Workflow Stage Changes | 4 | Track workflow progression |
| Approvals | 3 | Manage content approvals |
| Datasources | 5 | Key-value data management |
| Datasource Entries | 5 | Manage datasource data |
| Tags | 5 | Content tagging |
| Internal Tags | 5 | Internal organization tags |
| Webhooks | 5 | Event notifications |
| Collaborators | 4 | Team member management |
| Space Roles | 5 | Permissions and access control |
| Tasks | 5 | Task management |
| Discussions | 3 | In-content discussions |
| Releases | 5 | Release scheduling |
| Scheduling Stories | 3 | Schedule story publishing |
| Presets | 5 | Content presets |
| Space | 3 | Space configuration |
| Activities | 2 | Activity logs |
| Branch Deployments | 3 | Deploy branch changes |
| Pipelines | 4 | Content pipelines |
| Extensions | 3 | Manage extensions |
| Field Plugins | 3 | Custom field types |
| Access Tokens | 4 | Token management |
| Component Folders | 2 | Organize components |
| Meta | 2 | Space metadata and info |
| Ping | 1 | Health check |
Tool Naming Patterns
Understanding tool naming helps you know what each tool does:
List/Search Operations
- Pattern:
fetch_*orretrieve_* - Examples:
fetch_stories,retrieve_collaborators - Purpose: Get multiple items, often with filtering
- Returns: Array of items
Single Item Retrieval
- Pattern:
get_* - Examples:
get_story,get_component - Purpose: Get one specific item by ID
- Returns: Single item object
Creation
- Pattern:
create_* - Examples:
create_story,create_workflow - Purpose: Create new items
- Returns: Newly created item
Updates
- Pattern:
update_* - Examples:
update_story,update_component - Purpose: Modify existing items
- Returns: Updated item
Deletion
- Pattern:
delete_* - Examples:
delete_story,delete_asset - Purpose: Remove items
- Returns: Confirmation or deleted item
Publishing
- Pattern:
publish_*orunpublish_* - Examples:
publish_story,unpublish_story - Purpose: Make content live or take it down
- Returns: Updated item with publication status
Counts
- Pattern:
count_* - Examples:
count_stories - Purpose: Get counts without fetching all data
- Returns: Number
Common Parameters
Many tools share common parameters:
Filtering & Search
search- Text search across contentfilter_query- Advanced filtering (Storyblok query language)by_slugs- Filter by story slugsby_uuids- Filter by UUIDsstarts_with- Filter stories by folder path
Pagination
page- Page number (default: 1)per_page- Items per page (default: 25, max: 100)
Sorting
sort_by- Field to sort byreverse_order- Reverse sort direction
Content Options
language- Specific language versionfallback_lang- Fallback language if translation missingresolve_relations- Resolve story referencesresolve_links- Resolve URL/Story links
Response Formats
Single Item Response
{
"story": {
"id": 123,
"name": "My Story",
"slug": "my-story",
"content": {...},
...
}
}
List Response
{
"stories": [
{ "id": 123, "name": "Story 1", ... },
{ "id": 124, "name": "Story 2", ... }
],
"total": 42
}
Pagination Metadata
Many list responses include:
total- Total number of itemsper_page- Items per pagepage- Current page
Error Handling
Common error types:
Authentication Errors
- 401 Unauthorized - API key invalid or missing
- 403 Forbidden - Token lacks required permissions
Not Found
- 404 Not Found - Item doesn't exist
Validation Errors
- 422 Unprocessable Entity - Invalid parameters
Rate Limiting
- 429 Too Many Requests - Rate limit exceeded
See Common Errors for solutions.
Best Practices
Use Filtering to Reduce Load
Instead of fetching all items and filtering in code:
fetch_stories with filter_query for better performance
Leverage Pagination
For large datasets, use pagination:
Fetch stories 100 at a time using pagination
Batch Operations
For bulk operations, process in batches to avoid rate limits.
Cache When Appropriate
Component schemas and space settings rarely change - cache them.
Getting Help
Can't find what you need?
- Conversation Starters - Ready-to-use examples
- Common Tasks - Frequently requested operations
- Troubleshooting - Common issues
- GitHub Issues - Report problems or request features
Related Resources
- Getting Started - Setup and configuration
- Guides - Task-based tutorials
- API Documentation - Storyblok Management API docs
Note: BlokMCP is a wrapper around the Storyblok Management API. For deeper API details, consult the official Storyblok documentation.