Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CREATOROS_API_TOKENYesValid API token for the CreatorOS backend.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
generate_blogC

Generate a professional blog post for a CreatorOS project.

generate_linkedin_postC

Generate a LinkedIn post for a CreatorOS project.

generate_youtube_scriptC

Generate a YouTube script for a CreatorOS project.

generate_instagram_captionC

Generate an Instagram caption for a CreatorOS project.

generate_twitter_threadC

Generate a Twitter/X thread for a CreatorOS project.

generate_newsletterB

Generate a newsletter for a CreatorOS project.

generate_emailC

Generate a professional email for a CreatorOS project.

rewrite_contentC

Rewrite existing content for a CreatorOS project.

summarize_contentC

Summarize existing content for a CreatorOS project.

expand_contentC

Expand existing content for a CreatorOS project.

humanize_contentC

Humanize existing content for a CreatorOS project.

generate_seo_titleC

Generate an SEO title for a CreatorOS project.

generate_meta_descriptionB

Generate an SEO meta description for a CreatorOS project.

list_generationsC

List saved generations for a CreatorOS project.

get_generationB

Open one saved CreatorOS generation by project and generation ID.

delete_generationC

Delete one saved CreatorOS generation.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 16 tools

Disambiguation4/5

Most tools are clearly differentiated by output format or transformation type, and each has a distinct purpose. The only mild overlap is between rewrite_content and humanize_content, which could cause occasional misselection.

Naming Consistency4/5

The set mostly follows a consistent snake_case verb_noun pattern, e.g., generate_linkedin_post, summarize_content, delete_generation. The main inconsistency is generate_blog rather than generate_blog_post, which breaks the pattern used by other platform-specific generators.

Tool Count4/5

Sixteen tools is slightly above the typical well-scoped range, but the count is reasonable for a content generation server covering multiple platforms and content operations. Each tool adds a distinct capability, so the size feels justified.

Completeness4/5

The tool surface covers generation for major content types, transformation of existing content, SEO metadata, and saved-generation lifecycle management. Minor gaps such as no update/rename operation for saved generations are workable and do not cripple core workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues