Skip to main content
Glama
306,627 tools. Last updated 2026-07-25 16:35

"Managing Social Media Content Creation Using Monday" matching MCP tools:

  • Semantic full-text search across all Social Cooks content (blog articles, guides, glossary, service pages). Returns the most relevant passages with their source URLs so you can cite them. Read-only — use it to answer questions about the agency's approach, methods, metrics and how-tos that the other tools don't cover.
    Connector
  • Lower-level media import tool for agents that need to persist media separately from publishing. For normal create/update flows, prefer passing attached, selected, generated, local, temporary, base64, or non-Postly media directly through postly_create_post or postly_update_post media_file fields so the user approves one publishing action. If the user wants generated media now but will publish in a later turn, call postly_upload_media immediately after generation so Postly stores a durable media URL instead of losing the temporary file reference.
    Connector
  • Use this when an AI agent needs to create, queue, or schedule a Postly post through the publishing pipeline, including social channels and email/newsletter targets. If media was attached, generated, selected, or supplied as a temporary/local file reference, pass it in media_file, media_file_2, and so on; the server uploads those files to Postly storage inside this same create action. If the user wants generated media published or scheduled, complete the generation and post creation in the same turn so the temporary file reference does not expire. For multi-platform posts, first resolve targets, call postly_get_channel_schema for unfamiliar social platforms, validate content, generate safe platform_posts metadata, and apply defaults. Email/newsletter targets require email_subject and body text. Ask the user only for missing media/assets, business facts, or compliance-sensitive choices that cannot be inferred. If the user asks to publish everywhere and some platforms remain blocked, offer to publish to ready channels while skipping blocked ones.
    Connector
  • Edit one of my own posts — text, media, or both. Media (optional): pass `media` to REPLACE the post's entire attachment set (same rules as create_post — each asset approved + owned + kind in {image, video}; up to 4 images OR 1 video, never both). Pass a new array to swap the images/video, pass `[]` to strip all media, or OMIT `media` to leave the current attachments untouched (text-only edit). Get asset_ids from `get_my_media` or `upload_media_from_path`. Attaching an AI-generated image does NOT change the post's text badge (db/64) — the image carries its own AI-generated marker. Returns the post's public media URLs (`media_urls`) so they can be displayed inline.
    Connector
  • Generate a video clip using AI (xAI Imagine, 3 credits). Supports text-to-video, image-to-video, MULTI-IMAGE video (up to 7 images combined), and video editing with native audio (voiceover, sound effects, music). Best for quick drafts, social clips, iterations, and audio-first content. For cinematic final deliverables, use generate_video_veo instead. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]
    Connector
  • Query marketing data and analyze any website — analytics, SEO, advertising, e-commerce, CRM, social media, site health & brand identity, competitive intelligence, content creation, and data visualization. Always use a single call, even when the question spans multiple data sources or channels (e.g., GA4 + Google Search Console + Google Ads + CRM). The server auto-routes internally to all needed sources and returns a combined response with the same depth and granularity as individual queries — do NOT split multi-source or multi-channel questions into separate calls.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Transform any blog post or article URL into ready-to-post social media content for Twitter/X threads, LinkedIn posts, Instagram captions, Facebook posts, and email newsletters. Pay-per-event: $0.07 for all 5 platforms, $0.03 for single platform.

  • Monday.com MCP — wraps the Monday.com GraphQL API (BYO API key)

  • Get this week's most popular/trending Canton Network content (CIPs, forum threads, docs, blog, etc.) ranked by an engagement score. Canton-specific — not general crypto/social/news trends. Use for 'what's hot/popular on Canton right now'; use get_recent_changes instead for a chronological 'what changed recently' feed.
    Connector
  • Creates a private Redu media space: a small NFS VM backed by a persistent volume, intended for WordPress/WooCommerce wp-content/uploads in autoscaling clusters. Prefer letting deploy_app/deploy_compose create this by passing create_media_space:true after plan_deploy approval; use this tool when manually preparing or reusing shared uploads storage.
    Connector
  • Publish content to social media platforms. MEDIA RULES: • mediaUrl must be a public HTTPS URL — NOT a local file path. • If the user shares an image/video in chat, call create_upload_session FIRST to get a browser upload link, then use the returned URL here. • Text-only works on: LinkedIn, Threads, X, Facebook. • Image required: Instagram, Pinterest. • TikTok supports one video or 1-35 Photo Mode images. • Video required: YouTube. Call validate_content to check before publishing.
    Connector
  • Get detailed content requirements for a platform. Returns: Character limits, media specifications, rate limits, and special notes. Call this when you need specifics like exact character counts, file size limits, or supported formats. The publish_content description has a quick reference, but this tool provides complete details.
    Connector
  • Generate a visual preview of how content will appear on each platform. USE THIS WHEN: • Before publishing to see how posts will look • To validate content against platform requirements • To check character counts, hashtag limits, and media requirements Returns an HTML preview mockup for each platform with validation results: • Character count vs limit • Hashtag count (Instagram has 30 max) • Media requirement check • Platform-specific warnings and errors
    Connector
  • Have a vetted human expert verify whether an external source, project, or claim is trustworthy. Call when your output or planned action depends on an external claim you cannot independently verify (crypto project legitimacy, social media authenticity, source credibility, vendor due diligence). Returns verdict, red flags, positive signals, confidence score.
    Connector
  • Find channels accepting community submissions. Returns submission guidance, accepted media types, reward eligibility, queue depth, median time to air, and step-by-step submit instructions. Use this to decide where to submit content. Read-only. No auth required.
    Connector
  • Fetch the full competitor analysis report as structured JSON. Reports contain: website snapshot, Wayback Machine history, SEO/traffic data (DataForSEO), social media presence, Product Hunt launches, GitHub stats, pricing, funding, AI-generated business insights, growth playbooks, and more. Args: job_id: ID from analyze_competitor(); status must be 'completed' Returns: The full report dict (nested structure), or {error} if not found / not ready.
    Connector
  • Get the full details of a single Todoist task / to-do item by its id, including content, description, project id, section id, priority, due date/datetime, labels, web URL, and creation time. Use after todoist_list_tasks to inspect one task.
    Connector
  • Who am I? Returns the signed-in account: email, @handle, plan + limits, counts of sites/domains/drives, and connected DNS providers. Call this first to orient before managing sites or domains.
    Connector
  • Update an existing broadcast's name, message content, or media before sending. The broadcast must still be in draft status.
    Connector
  • Render one public Wiplash post as an interactive, read-only view with its media, active feedback, and related posts. Use a post ID returned by search_posts or get_post. The renderer never executes post, app, SVG, or code content.
    Connector