FavCRM

This connector has been deprecated

This connector has been replaced by https://glama.ai/mcp/connectors/io.favcrm/favcrm/admin

create_post

Create a new CMS post (blog_post, page, or any custom post type). The post type must already exist — use list_post_types to discover, create_post_type to add a new one. excerpt = plain-text summary only (auto-derived from blocks if omitted). Structured custom fields go in meta, keyed by the field schema defined with create_post_type_field.

Input Schema

TableJSON Schema

Name	Required	Description
`meta`	No	Structured custom field values, keyed by field key (see list_post_type_fields). Validated against the post type field schema. Use this for all machine-readable data — never put JSON in excerpt.
`slug`	No	URL slug. Auto-generated from title if omitted; collisions get -2, -3 suffix.
`type`	Yes	Post type slug (e.g. blog_post, page, treatment). Must exist in post_types for this company.
`title`	Yes	Post title
`blocks`	No	Ordered array of content blocks. Each block has { id, version, type, data } where type is one of: paragraph, heading, image, list, quote, code, divider, spacer, embed, html, youtube, file, faq, callout, gallery, cta, accordion, product, columns. Unknown types are rejected.
`status`	No	Status (default draft)
`tagIds`	No	Tag IDs to attach to the post
`excerpt`	No	Plain-text summary only — never JSON. Auto-derived from the first paragraph/heading block if omitted and the post type supports excerpts.
`parentId`	No	Parent post ID for nested types (e.g. pages).
`seoTitle`	No	SEO title override
`sortOrder`	No	Sort order (lower = earlier)
`visibility`	No	Visibility (default public)
`categoryIds`	No	Category IDs (post types with supportsCategories only)
`publishedAt`	No	ISO timestamp; required when status=scheduled.
`featuredImage`	No	Cover image URL
`seoDescription`	No	SEO meta description

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Tool result payload — shape varies per tool, see the tool description
`summary`	Yes	One-line human-readable summary of the action
`renderType`	Yes	UI rendering hint for the result

TDQS

A4.1/5.0

Behavior4/5

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

Annotations indicate a non-read-only, non-idempotent creation operation, which matches the description. The description adds useful behavioral details such as auto-derived excerpt from blocks, slug auto-generation with collision handling, and a warning against placing JSON in excerpt, going beyond what annotations provide.

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

Conciseness5/5

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

The description is front-loaded with the core purpose and uses concise sentences. Every sentence adds specific value (prerequisites, auto-derivation, meta usage). No redundant or fluff content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high schema coverage and the existence of an output schema, the description covers the essential workflow: prerequisites, parameter behaviors, and warnings. It does not explain return values, which is acceptable. It provides sufficient context for an agent to use the tool correctly.

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 description coverage is 100%, but the description adds value by clarifying excerpt behavior and the expected structure for meta. It also warns about JSON misuse, which is not present in the schema. This provides meaningful context beyond the schema definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a new CMS post, specifying the supported post types (blog_post, page, custom). It mentions related tools (list_post_types, create_post_type) for discovery, which helps distinguish it from sibling tools, though it could explicitly contrast with update_post.

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?

It explicitly states prerequisites: the post type must already exist, and guides the user to list_post_types or create_post_type if needed. It also explains how to handle custom fields via meta. However, it does not mention when to use alternatives like update_post or clone.

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

All FavCRM tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation5/5

Each tool targets a distinct resource and action, with clear descriptions that minimize ambiguity. Even related tools like create_post vs create_post_type are well-separated by their targets.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., create_account, list_services, update_post), with no mixing of naming conventions. The pattern is predictable throughout the set.

Tool Count1/5

190 tools is excessively large for any server, far exceeding the typical 3-15 tool range. The sheer volume overwhelms agents and suggests poor scoping, even for a comprehensive CRM platform.

Completeness4/5

The tool set covers CRUD operations across many domains (CRM, bookings, marketing, CMS, etc.), but notable gaps exist (e.g., no delete_account, delete_contact, update_booking). These are minor given the vast surface.

Resources

Need Help?