fix: v1.0.2 — drop /v1 prefix (live production bug) + add new tool params

[OussemaFr]

TL;DR

• v1.0.1 has a critical bug — server.js defaults to https://api.socialapis.io/v1 but the real API has no /v1 prefix. Every npm-installed MCP customer has been 404'ing since the 2025-12-18 publish.
• This PR fixes the URL and adds tool-schema updates for the new params shipped on the main API (limit, exact_followers_count) so MCP clients surface them correctly.

The critical bug

server.js line 7:

```diff

• const API_BASE_URL = process.env.API_BASE_URL || 'https://api.socialapis.io/v1';

• const API_BASE_URL = process.env.API_BASE_URL || 'https://api.socialapis.io';
  ```

Verified against production: `curl https://api.socialapis.io/facebook/pages/details?...\` returns 200; the same path with `/v1` prefix 404s.

Tool schemas updated

Tracking the recent additions to the main repo's `endpoints.json` (per Minima-Partners/Social-APIs PR #183 and follow-ups):

Tool	Change
`facebook_get_page_details`	+ `exact_followers_count` (boolean, charges 5cr when true)
`facebook_get_page_posts`	+ `limit` (number, default 3, min 3, max 9, scaled pricing)
`facebook_get_group_posts`	+ same `limit`
`facebook_get_page_videos`	+ `limit` (default 6, min 6, max 12)
`facebook_get_post_comments`	+ `limit` (default 10, max 30)
`facebook_marketplace_search`	+ `limit` (default 24)
`facebook_get_post_attachments`	description: 5 credits/call

Numeric limits use JSON Schema `minimum`/`maximum` so MCP clients can surface bounds at parameter-edit time.

Sanity check passed

• 47 unique tools (was 47, still 47 — no duplicates added)
• 0 tools with `required` references to properties not defined in `properties`
• `package.json` version bumped 1.0.1 → 1.0.2

```bash
node -e "import('./src/tools.js').then(({tools}) => {
const dups = tools.filter((t,i,a) => a.findIndex(x=>x.name===t.name)!==i);
const broken = tools.filter(t => (t.inputSchema?.required||[])
.some(r => !(r in (t.inputSchema?.properties||{}))));
console.log('dups:', dups.length, 'broken:', broken.length);
})"

→ dups: 0, broken: 0

```

Publish steps after merge

1. `npm publish` — needs operator with npm publish access on `@socialapis/mcp` (no Trusted Publishing wired here yet; consider adding a release workflow next time).
2. Tag the release: `git tag v1.0.2 && git push origin v1.0.2`.
3. MCP Registry auto-syncs from npm via the `mcpName: io.github.SocialAPIsHub/social-media-api` field — should pick up v1.0.2 within ~24h.
4. Update the main repo's `backend/mcp-server` submodule pointer to this commit (separate PR in Minima-Partners/Social-APIs).

Test plan post-publish

```bash

Install the new version

npm install @socialapis/mcp@1.0.2

Quick smoke test — should not 404

SOCIALAPIS_API_KEY=<your_key> npx @socialapis/mcp test-key
```

In Claude Desktop / Cursor with the MCP server configured, calling `facebook_get_page_details` with `exact_followers_count: true` should charge 5 credits (visible in the `X-SocialAPIs-Credits-Deducted` response header).