ShowMeStepByStep
Server Details
Search, browse, and cite a 377-tutorial step-by-step how-to corpus from your AI client.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 6 of 6 tools scored.
Each tool has a clearly distinct purpose: fetching a tutorial by slug, listing categories, recent tutorials, tutorials by category, submitting a request, and searching. No overlap in functionality.
All tools follow a consistent verb_noun pattern in snake_case (e.g., list_categories, search_tutorials). No mixing of conventions or vague verbs.
With 6 tools, the server is well-scoped. It covers the essential operations for a tutorial discovery service (search, browse, details, request) without unnecessary bloat.
The tool set covers the full lifecycle needed: search, browse by category and recency, fetch details, and request missing content. No dead ends or missing operations for the stated purpose.
Available Tools
6 toolsget_tutorialInspect
Fetch the full machine-readable rendition of a tutorial by slug: title, TL;DR, numbered steps (with text, imageUrl, tips, and YouTube videoTimestampSeconds for deep-linking), tools/materials, tags, related tutorial slugs, creator credit, recipe (with nutrition + cuisine when applicable), license, and canonicalUrl. Use this after search_tutorials to fetch step details.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Tutorial slug (e.g. 'how-to-fix-a-leaky-faucet') |
list_categoriesInspect
List all tutorial categories with a published tutorial. Returns slug, name, short description, and count of published tutorials per category.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_recent_tutorialsInspect
List the most recently published tutorials, newest first. Use this to discover what's new on the site or to surface fresh content for aggregator / 'what's new this week' agent loops. Tenant-aware.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Lookback window in days (default 14, max 90). | |
| limit | No |
list_tutorials_by_categoryInspect
Browse tutorials within a specific category, ranked by view count then publish date. Use this when a user wants to explore a topic area rather than search.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| categorySlug | Yes | e.g. 'cooking', 'home-improvement', 'crafts' |
request_tutorialInspect
Submit a request for a tutorial we don't yet have. Call this when search_tutorials returned no good match for what the user actually wants. The request enters our content-demand queue, which the daily content batch reviews and prioritizes. Optionally include an email for notification when the tutorial ships.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | What the user wants to learn how to do (e.g. 'how to get pesto stains out of a white shirt') | |
| context | No | Brief context about the requester (e.g. 'beginner crocheter', 'first-time homeowner', 'gluten-free baker'). Helps shape the tutorial when we ship it. | |
| notifyEmail | No | Optional email to notify when the tutorial ships. Pure opt-in. | |
| originalQuery | No | The exact user query that came up empty in search_tutorials. Useful for matching keyword demand. |
search_tutorialsInspect
Search the ShowMeStepByStep tutorial corpus by free-text query. Searches across tutorial titles, descriptions, and step content. Returns slim summaries with TL;DRs and canonical URLs. Tenant-aware. Optional filters narrow by category, difficulty, or maximum duration.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | Search query (>= 2 chars) | |
| difficulty | No | Optional difficulty filter. | |
| categorySlug | No | Optional category to restrict the search to (e.g. 'cooking', 'crochet'). Use list_categories to see available slugs. | |
| maxDurationMinutes | No | Optional ceiling on tutorial total duration. Useful for 'quick recipes' / 'under 10 min' queries. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!