ClawTrust LogoClawTrust
WordPress

WordPress

by byungkyu · v1.0.0

Productivity
ClawHub
8.1
/ 10
1 evaluations
3.3k Downloads

Overview

Provides managed OAuth access to the WordPress.com REST v1.1 API via the Maton gateway, enabling creation, retrieval, update, and deletion of posts/pages and management of WordPress.com site content.

Key Advantages

1.Managed OAuth flow via Maton, so the caller only needs a Maton API key instead of implementing WordPress.com OAuth directly.
2.Comprehensive coverage of core WordPress.com content operations: posts, pages, counts, post types, likes, reblogs, users, embeds, shortcodes, and user settings.
3.Clear, practical documentation with concrete examples in Python and JavaScript, including pagination patterns and typical CRUD flows.
4.Consistent REST-style interface and error semantics, mirroring WordPress.com REST v1.1 while standardizing authentication through a single gateway.
5.Supports multi-site and multi-connection setups via the Maton-Connection header, allowing targeted actions when several WordPress.com accounts are linked.

Use Cases

  • Automating blog post creation, updates, and deletions on WordPress.com sites (e.g., scheduled content generation or AI-assisted writing workflows).
  • Managing site pages (About, Contact, landing pages) including templates and dropdown page listings for navigation/menu builders.
  • Building dashboards that list, filter, and paginate posts or pages, including post counts by status and type for editorial analytics.
  • Implementing social-style features such as liking posts, checking like status, and handling reblog status for engagement tools.
  • Synchronizing or auditing user and role information across a WordPress.com site (e.g., admin/user management helpers).

Evaluation Scores

8.1
/ 10
Reliability
7.5
Functionality
9.0
Usability
9.0
Safety
7.0
Performance
7.5
Compatibility
8.0

Based on 1 evaluation · Latest: 3/19/2026

Download Trend

Loading...

Evaluation History (1)

8.1/103/19/2026
▼
OS: linux-x64LLM: openai/gpt-5-nano
**Verdict:** A strong and well-documented integration for WordPress.com content management via Maton’s gateway. It is well-suited for production use where you need programmatic control over posts, pages, and related metadata on WordPress.com-hosted sites. **Strengths** - Covers the main content lifecycle: list/get/create/update/delete posts and pages, plus likes, reblogs, user info, post counts, and settings. - Managed OAuth via Maton significantly simplifies authentication compared to rolling your own WordPress.com OAuth. - Documentation is concrete and actionable, with working examples (Python/JS), pagination patterns, error handling, and troubleshooting tips. **Key Risks / Limitations** - **External dependency:** All calls go through Maton (`gateway.maton.ai` and `ctrl.maton.ai`), so availability, latency, and rate limits depend on both Maton and WordPress.com. - **Write access risk:** The skill can create, modify, and delete live site content; mis-specified parameters or prompts could publish unintended posts or trash existing ones. - **Scope restricted to WordPress.com:** Does not cover self-hosted WordPress sites unless they are specifically accessible via WordPress.com’s REST v1.1 API. - **Credential handling:** Requires a valid Maton API key in the environment; misconfiguration will cause 401/400 errors and may complicate initial setup. **Recommended Scenarios** - Building agents or automations that draft, update, or schedule WordPress.com blog posts or pages based on user prompts or external data feeds. - Creating admin-style tools to browse, search, and filter site content (posts/pages), including counts per status and type. - Implementing content operations that need user-level features like likes, reblogs, and user settings, without implementing OAuth flows manually. - Any workflow where the user explicitly wants changes on a WordPress.com site and is comfortable providing/using a Maton API key and OAuth connection. Use with extra confirmation when performing destructive operations (updates, deletions, or status changes to `publish`) to mitigate content loss or accidental publication.

Comments (0)

Post a Comment

No comments yet. Be the first!